Generate deployments from merged pull requests
The simplest proxy for deployments is to assume a merged pull request is immediately deployed.
Looking to get started with DORA metrics? Tracking how often a team deploys and the quality of these deploys is often not a trivial task. It's difficult to get a perfect solution right away, and often it's better to aim for a solution as the first step.
PR merge based deployments are only supported if you directly merge to the selected deploy branch. If you have automation that initiates deploys without pull requests based on a single branch, then you need to use GitHub checks or the Deployments API to inform Swarmia about deployments.
We backfill deployment data for the past 90 days.
Limitations
Using PR merges as the deployment source has the following limitations:
Time to deploy is not available. This is because we only know when the PR was merged, but don't get any signal when it is in production. This means that the change lead time will be equal to the pull request cycle time.
Automatic rollback detection is not available. This is because we don't get the deployed version numbers from PR merges.
Configuration
Deployments can use Pull Request merges as the input data.
Start by creating an application and giving it a name
Select "Pull request merge creates a deploy" as the Deployment source.
Select repository
Select the branch (or branch prefix) that most accurately represents your production deployment events. You can give this environment a name, although we recommend "production".
Optional: Add more environments based on the branch name or prefix. This allows you to view deployments from different environments on the Metrics → DORA → Deployments page.
Confirm the amount of deployment data to be created, and Save.
Last updated
Was this helpful?