Generate deployments from GitHub deployments
If your release workflow already makes use of GitHub deployments, Swarmia can automatically track those deployments.
Last updated
Was this helpful?
If your release workflow already makes use of GitHub deployments, Swarmia can automatically track those deployments.
Last updated
Was this helpful?
can use Check runs from as the input data.
and giving it a name
Select "GitHub deployments" as the Deployment source.
Select the repository from which you you want to track deployments.
Confirm the amount of deployment data to be created, and Save
If you use GitHub deployments, Swarmia automatically configures the deployment apps for you if there's no existing app with the same name. Contact us at hello@swarmia.com if you'd like to disable this behavior.
GitHub deployment statuses (error, failure, inactive, in_progress, queued, pending, and success), on the other hand, are meant for communicating the status of getting code to production. If a GitHub deployment has the status error or failure, it means that you failed to deploy code to production, not that you caused a change failure. Because of this, Swarmia only ingests deployments when they have the status success.
In order to generate GitHub deployments for your deployment workflows, ensure that the workflows indicate an environment (e.g production) as instructed by GitHub deployments . The generated deployments then reflect on https://github.com/<organization>/<repository>/deployments as shown in this example.
The failed/succeeded deployment status in Swarmia's DORA/Deployment insights is communicating if a change (= piece of code) that you deployed to production caused a change failure. In other words, if it caused a failure in production (that needed a fix in the form of a rollback, forward fix, etc.). This information is based on data.
