Respond to a failed release
When a release run fails, Jaah records it as an incident of type Release failed, named after the workflow, the environment and the job that failed. A second failure of the same job adds to that incident's Count instead of adding a new one. This guide starts from that incident and ends when a good release resolves it. To check a release that finished but may have broken production, see Check whether a release broke production.
Before you start: Production QA is a plan feature. While your plan does not include it, Incidents is left out of the side menu and opening the page shows Not on your plan. Failed releases are recorded only for a project whose releases are connected: see Turn on Production QA for a project.
Who can do this: anyone who can view the project.
- Select Incidents in the side menu.
- Set Type to Release failed and pick the Project. Set State to Open to hide the ones a later release already fixed.
- Select the incident's title. It opens on Overview. Read:
- Environment: where the release was going.
- Count and Last seen: how many runs failed this way, and when the latest did.
- Commit: the commit the failed run released. Point at it for the full hash.
- To read the log, select the run under Vendor link. It opens the failed run in your repository host.
- To see what the run was releasing, select the number under Jaah release. The release's page lists:
- Failed at: the job and step that failed.
- PRs: the pull requests in the run. One made by a task links to that task.
- Run: the same run in your repository host.
- Back on the incident, select the Tasks tab. With the project's Production QA switch on and its Release failed automation in place, Jaah files a task for the failure and links it here. No tasks filed means none was; fix the cause yourself, or start a task for it.
- Once the fix is merged, release again. See Release to production for releasing after a failure. A release that failed before its merge, such as on red checks, can be sent again as it was: see Retry a failed release.
- Check the incident. The next successful run of the same workflow to the same environment marks it Resolved, and the History tab shows when. The page refreshes every 15 seconds.
Related
- Release runs — every field and tab on the page of a release.
- Incidents — the Incidents page and every tab of an incident.
- How Production QA works — releases, incidents, and when an incident becomes a task.