The DevOps Report gives you an overview of your entire instance’s adoption of Concurrent DevOps from planning to monitoring.
To see DevOps Report, go to Admin Area > Analytics > DevOps Report.
The DevOps Score tab displays the usage of major GitLab features on your instance over the last 30 days, averaged over the number of billable users in that time period. It also provides a Lead score per feature, which is calculated based on GitLab analysis of top-performing instances based on usage ping data that GitLab has collected. Your score is compared to the lead score of each feature and then expressed as a percentage at the bottom of said feature. Your overall DevOps Score is an average of your feature scores. You can use this score to compare your DevOps status to other organizations.
The page also provides helpful links to articles and GitLab docs, to help you improve your scores.
Usage ping data is aggregated on GitLab servers for analysis. Your usage information is not sent to any other GitLab instances. If you have just started using GitLab, it may take a few weeks for data to be collected before this feature is available.
Introduced in GitLab 13.7.
The DevOps Adoption tab shows you which segments of your organization are using the most essential features of GitLab:
- Merge Requests
Segments are arbitrary collections of GitLab groups that you define. You might define a segment to represent a small team, a large department, or a whole organization. You are limited to creating a maximum of 20 segments, and each segment is limited to a maximum of 20 groups. Buttons to manage your segments appear in the DevOps Adoption section of the page.
DevOps Adoption allows you to:
- Verify whether you are getting the return on investment that you expected from GitLab.
- Identify specific groups that are lagging in their adoption of GitLab so you can help them along in their DevOps journey.
- Find the groups that have adopted certain features and can provide guidance to other groups on how to use those features.
DevOps Adoption is deployed behind a feature flag that is enabled by default. GitLab administrators with access to the GitLab Rails console can opt to disable it.
To disable it:
To enable it: