Find out why a release's probes did not run
After each successful production release, Jaah runs the project's health URLs and smoke commands as a task. When a release's Probes tab shows no Passed or Failed results, its Run line says whether that task is still going or why it did nothing. To set probes up in the first place, see Check production after every release.
Before you start: the release run pages are part of Production QA, a plan feature. While your plan does not include it, opening the page of a release shows Not on your plan.
Who can do this: anyone who can view the project. Turning on Production QA for the project needs permission to edit it.
- Open the release's page. Release runs lists every way in, from the project's pipeline on the Tasks page or from an incident.
- Check the status beside the project and environment. Probes run only after a release that Succeeded.
- Select the Probes tab.
- Read the Run line. It starts with the task that runs the probes; select its number to open the task.
- Running: the probes are under way. The page refreshes every 15 seconds, and Results fills in when the task reports.
- A time: the task reported then. Its results are under Results.
- Any other state after the task, such as System failed: the task ended before it reported. Open it to see what happened.
- Look for a Skipped: reason at the end of the Run line, and act on it:
- Skipped: Production QA off or Skipped: project not opted in: Production QA was on when the release shipped, so Jaah filed the probe task, but it was turned off for your organization or for the project before the probes ran. Nothing was probed. To probe the next release, check the project's switch as in Turn on Production QA for a project.
- Skipped: a later release superseded it: a newer release came out before these probes ran, so Jaah probed that one instead. Open the newer release from the project's pipeline and read its Probes tab.
- If the tab reads No probe results, no probe run was filed for this release at all. Check that the project's Production QA switch was on when the release shipped, as in Turn on Production QA for a project, that the project lists health URLs or smoke commands, as in Check production after every release, and that the release went to production.
Related
- Respond to a failed health check: when a probe ran and failed.
- Release runs: every field on the Probes tab.
- How Production QA works: when Jaah records and when it acts.