Status monitoring and feedback
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Description
When I merge a MR, it's good to know that when this MR is deployed, this commit didn't blow up that environment.
Proposal
Report whether a MR blew up an environment (made it non-reachable) in the MR and the environments view.
This can come with a link to revert that commit from the branch that is being deployed to that environment.
Example
I merge a change into staging, which deploys to the staging environment.
Once my change is deployed to staging, GitLab pings the environment and doesn't receive a 200 status.
In the MR and the environment, GitLab reports that the environment is down and that the last deploy introduced the change of my MR and offers to revert it.
Links / references
cc @markpundsack @sytses @victorwu
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.