"Freeze Environment when its target environment gets an alert
Problem to solve
As a developer deploying new code, I would want to cancel deployment if the new code exceeds a specific error threshold rate, so that I do not expose faulty code to a larger audience.
Intended users
User experience goal
The user should be able to stop rolling out a bad deployment (and in the future auto-rollback) by using CD with the combination of Monitoring feature
Proposal
- Add a freeze deployment button to each environment. This button does:
- Cancels the rollout of a deployment
- Freezes any future rollouts to this environment until the freeze is lifted.
- Only users that are allowed to deploy to the environment should be able to press the cancel button | The button should be hidden/disabled for other users
- The button is available regardless of an alert being present yes or no.
| Wireframe mockup (Figma document) |
|---|
 |
Further details
Based on the research conducted in #214630 (comment 338226324) we will take advantage of this existing mechanism to trigger the pipeline to stop roll-out.
Permissions and Security
Only users that are allowed to deploy to the environment should be able to press the cancel button.
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
This is a cross stage feature with devopsmonitor
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.