Present the number of rollbacks that were done from produciton
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
As an executive investing in DevOps, I want to see my ROI. I want to see an improvement in the deployment frequency of my dev team. This will most likely drive the KPIs of my team.
As a developer leader I want to see that the team is improving by measuring the deployment frequency and comparing it over time (over sprints)
Intended users
User experience goal
Today we show https://gitlab.com/gitlab-org/gitlab/-/value_stream_analytics
We already present deployment frequency as a numerical value but we need to show this in a chart view - as the trend is the most interesting aspect of this metric.
Proposal
We should support the number of rollbacks from production both in API and on UI
The way that users rollback today is by selecting an old deploying and pressing re-deploy
We can count a rollback by counting the number of older deployments that are deployed
- Add to overall statistics under change failure rate
- Present a chart for deployment frequency for daily periods for the past week
- Present a chart for deployment frequency for daily periods for the past month
- Present a chart for deployment frequency for daily periods for the past year
Further details
Permissions and Security
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?
gitlab3103458d gitlab4116705 devopsrelease [DEPRECATED]
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.