Flow A - Notification > Deployment Template Machine and Runbooks
Flow for Release Mock
- User receives a notification from Slack or email that a deployment has been rollback automatically with a link to the failed job and an option to see the environment.
- User follows link to the environment which pulls them into a dashboard where failed deployments are collected at the top followed by the option to filter on environment status and they see this one deployment that failed with active rollback alert
- Click on the active rollback alert and it highlights the step in the runbook connected to the deploy job that identified a threshold of security scans and test failures was reached after a deploy was made and it kicked off an auto-rollback.
- GitLab links issues created from failure to deployment tile and allows user to assign issue to user and milestone from that screen
- Slack sends another notification to group that issue for failure is assigned to person and is due on x milestones
- On the prior screen, a suggestion alert is added where GitLab suggests you may want to fix your deployment template to validate pre-deployment the quality and security (or performance) thresholds with a link to the template machine, where a user takes advantage of the Template Machine under the Operations tab at the Group-level
- User can update template and save which then automatically updates the deployment pipelines in the active jobs to validate
- Go back to dashboard to see a new commit on all environments using template called Add step for Validating Pre Deployment