You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0a0797f
Browse filesBrowse the repository at this point in the historyBrowse files
Update a deployment's change failure status, identifying the deployment by its service, environment, and version instead of its ID. Use this to mark a deployment as a change failure or back to stable. You can optionally include remediation details to enable failed deployment recovery time calculation. If multiple deployments match the given service, environment, and version, the most recently finished one is updated.
Copy file name to clipboardExpand all lines: tests/v2/features/dora_metrics.feature
+3-6Lines changed: 3 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -149,27 +149,24 @@ Feature: DORA Metrics
149
149
Then the response status is 200 OK
150
150
151
151
@generated@skip@team:ddoghq/ci-app-backend
152
-
Scenario:Patch a deployment event by version returns "Accepted" response
152
+
Scenario:Mark a deployment as failed by version returns "Accepted" response
153
153
Given a valid "appKeyAuth" key in the system
154
-
And operation "PatchDORADeploymentByVersion" enabled
155
154
And new "PatchDORADeploymentByVersion" request
156
155
And body with value {"data": {"attributes": {"change_failure": true, "env": "production", "remediation": {"type": "rollback", "version": "v1.2.2"}, "service": "my-service", "version": "v1.2.3"}, "type": "dora_deployment_patch_request"}}
157
156
When the request is sent
158
157
Then the response status is 202 Accepted
159
158
160
159
@generated@skip@team:ddoghq/ci-app-backend
161
-
Scenario:Patch a deployment event by version returns "Bad Request" response
160
+
Scenario:Mark a deployment as failed by version returns "Bad Request" response
162
161
Given a valid "appKeyAuth" key in the system
163
-
And operation "PatchDORADeploymentByVersion" enabled
164
162
And new "PatchDORADeploymentByVersion" request
165
163
And body with value {"data": {"attributes": {"change_failure": true, "env": "production", "remediation": {"type": "rollback", "version": "v1.2.2"}, "service": "my-service", "version": "v1.2.3"}, "type": "dora_deployment_patch_request"}}
166
164
When the request is sent
167
165
Then the response status is 400 Bad Request
168
166
169
167
@skip@team:ddoghq/ci-app-backend
170
-
Scenario:Patch a deployment event by version with a missing version returns "Bad Request" response
168
+
Scenario:Mark a deployment as failed by version with a missing version returns "Bad Request" response
171
169
Given a valid "appKeyAuth" key in the system
172
-
And operation "PatchDORADeploymentByVersion" enabled
173
170
And new "PatchDORADeploymentByVersion" request
174
171
And body with value {"data": {"attributes": {"change_failure": true, "env": "production", "service": "my-service"}, "type": "dora_deployment_patch_request"}}
0 commit comments