Skip to main content

Find a release run by environment or status

The Production section of a project's pipeline shows its releases, but not every run your repository host makes: a run to a test environment may belong to no release. Runs lists them all, newest first, for any environment. Use it to find last night's run to staging, or every run that failed this week. What Jaah records about each run is in How Production QA works.

Before you start: Runs and the run pages are part of Production QA, a plan feature. While your plan does not include it, Runs is not shown and opening the page of a release shows Not on your plan. Runs appear only once the project's releases are connected: see Turn on Production QA for a project.

Who can do this: anyone who can view the project.

  1. In the sidebar, select Tasks, then select the project in the Projects tree.
  2. At the top of the page, select Pipeline, and scroll to the Production section.
  3. Under the releases, select ▸ beside Runs to open it. Each row shows the environment, its status and how long ago it finished or started.
  4. To narrow the list, pick an environment in Environment (Any environment shows all), and a status in Status (Any status shows all): Queued, Releasing, Succeeded, Failed, Cancelled or Skipped. A failed row also names the job and step that failed.
  5. Select a row to open that run's page beside the board.
  6. On Overview, read Environment, Range and PRs for what it shipped, Failed at for where it broke, and Started and Finished for when it ran. Run opens the run in your repository host to read its log.

No runs means the project has no run in that environment or status. The list refreshes every 15 seconds while it is open. For a run that failed, follow Respond to a failed release; for one that succeeded, Check whether a release broke production.