What is Deployment Frequency?
Deployment Frequency uses your Github Actions data to calculate the number of successful deployments to production a group of people has in a given time period. It is an indication of how frequently and consistently teams are able to deliver new value to customers and end-users. Monitor this data in your Uplevel Dashboard to make sure your teams are deploying regularly.
How are Deployments to Production Defined?
Deployments to production are estimated for each repository by the environments configured within Github Actions. Uplevel uses an organization wide regular expression (Regex) to find for production environments, but exclude non-production environments. An example is shown below that looks for environments that contain the strings prod|live|release, but excludes pre-prod|pre-release and other variants, as well as explicitly excluding qa and staging environments.
Your organization's global definition is visible by visiting the configuration page, and clicking on an environment. Learn more about how to utilize this page here. Getting production environments to reflect the way code is deployed to end users is very important to ensure that Uplevel's DORA metrics are accurate for your team. This can be configured in two ways
Changing the global definition:
Reach out to our Customer Success team to build your organization's global Regex. Your organization might have specific keywords that should be included or excluded, and the Uplevel team can customize how this works on a global level to match the way you work.
Specific Repository Definitions
It is also possible that certain repositories break the global rules, and need specific overrides. Reach out to our Customer Success team and we can make specific rules at the repository levels that will persist even when the global definition changes.
💡Example: Most repos use dev as a development environment, however for a handful of repositories, dev is actually a production branch that end users access. The global rule can be overridden for these specific repositories without touching the rest of the org.