Deployment outcome

Step by step

1. Inspect the pipeline run DevOps Engineer

   DevOps Engineer reads the branch, commit, start and finish time, status and service. A Passed result supports the delivery decision; a Failed result calls for investigation before the release proceeds.

   • Shows commit, branch and run result
   • Updates Pipeline runs, Services

2. Confirm the change Release Manager

   Release Manager checks the approved change, its scheduled window and rollback plan. The CAB decision explains why the release was authorized. The engineer uses that context when choosing the implementation window.

   • Checks approved service work and review decision
   • Updates Changes, CAB reviews

3. Start the deployment DevOps Engineer

   When the change moves into implementation, the workflow records a pending deployment. The engineer identifies the service, environment and version on the deployment record.

   • Records pending environment work
   • Updates Changes, Deployments

4. Record the result DevOps Engineer

   DevOps Engineer updates the deployment status to the observed outcome. Healthy, Failed and rolled back have different meanings. A rollback reference and checkpoint result help explain a reversal.

   • Preserves actual outcome and checkpoint evidence
   • Updates Deployments, Rollback checks

5. Verify the change Release Manager

   Release Manager compares the deployment service and time with the change window, checks the recorded environment and version, then marks the change verified or rolled back as appropriate. A pipeline pass alone does not complete this review.

   • Closes the planned change against the observed result
   • Updates Changes, Deployments

DevOps Engineer

, Release Manager, CAB Reviewer, Admin.