Pipelines
The Pipelines table, its run statuses, the status filter and sorting.
The Pipelines page lists every run from every connected provider. Every role can open it.
Deployments across deployment environments (pending approvals, what is running, history) are on the Gates page, not here.
The table
The page fits your screen and scrolls inside the table. Columns: Status, Cause, Workflow, Trigger, Repository, Branch, Commit, Actor, Environment, Started, Duration and Jobs. Cause shows a failed run's failure category and Passed on retry when a later run on the same commit, or a later attempt of the run, passed. It is left out when the Status filter shows neither failed nor successful runs.
On a phone the table becomes a compact list: status, workflow and run number, age, repository and branch, and duration. Tap a run to expand it.
The repository, branch, commit and actor in a row link to the provider. Click the workflow name to open the run's page, or click the row to expand it.
Old links with or open the table. An old link to an approval opens that approval on the Gates page's Awaiting approval tab.
Run statuses
Every provider's statuses are mapped to one set that Prodgator uses everywhere:
| Status | Includes |
|---|---|
| Running | Runs in progress |
| Awaiting approval | Runs paused on a deployment approval or a manual action |
| Success | Completed successfully |
| Failed | Failed or timed out |
| Queued | Created but not started yet |
| Cancelled | Cancelled, stopped or skipped |
The per-provider mappings are on each adapter page.
Status filter
The Status filter narrows the list by run state. Tick one or several states, for example Running and Awaiting approval together. The states are Running, Awaiting approval, Success, Failed, Queued and Cancelled. All clears the choice. Each state shows how many runs match. A count like means there are at least that many.
Sorting
In the table, click Status, Workflow, Repository, Started or Duration to sort. Click again to reverse. Sorting orders the runs on the current page. It does not re-sort the whole history.
Empty and error states
- No pipelines connected yet: no run has arrived and no provider is connected. Admins see a Connect provider button in place of the table. Once there are runs, the button is gone, even if you later disconnect every provider.
- No runs yet: a provider is connected but has not reported a run. There is no button.
- No pipelines found: no run matches your search and filters. Click Clear Filters.
- Couldn't load pipelines: Prodgator could not reach its API. Click Try again.