Three of the DORA Metrics (Deployment Frequency, Lead Time for Changes, and Change Failure Rate) are all measured using CI/CD data, and specifically deployments to production environments.
The deployment data is generated from GitHub Actions, as well as Jenkins (coming soon!). To understand how Uplevel is estimating which environments are considered production environments, head to the Repository Settings page.
This page is scoped to the segment selected (Organization), as well as the date range (June 24 to September 15th). This show the repositories that have had the most Total Deployments by default, as well as the number of merged PRs so that users can find the most active repositories for their team.
Each row of repositories shows the number of production environments that Uplevel estimates, as well as the last time code was deployed in that repository. Clicking a repository will show the specific environments, what we consider to be production, and how many deployments happened in the time window.
💡Example: For
uplevel-web
, there have been 389 PRs merged by the Uplevel team in the past 3 months, with 464 total deployments. Most of these have been to our staging environment, with 41 deployments to ourproduction
environment. Staging is not considered a production environment, so the 423 deployments are not counted in our Deployment Frequency metric, Lead Time for Changes, and Change Failure rate metrics.
Click a specific environment to see why an environment was considered production, and learn more about how to configure your specific production environments here.
Note that the number of PRs merged are authored by members of the selected Segment, but the Total Deployments can be done by anyone using that repository, including those outside the selected segment. For example, deployments of code to production might be initiated by bots, or members of a different team.