Release Pipelines
Put named, approved stages between a report being edited and a report being trusted.
By default, publishing a report sends it straight to production. A release pipeline inserts stages in between — test, uat, prod, or whatever your organization calls them — each with its own approvers and its own live version.
Creating a Pipeline
From Release Pipeline in the admin console, click Add new release pipeline and name it. The pipelines table shows each pipeline's Name and Num Stages, with actions to view its stages or delete it.
Adding Stages
Open a pipeline to see its stages in order. Click New step between two stages to insert one, and provide:
| Field | Meaning |
|---|---|
| Name | The environment name for this stage — this is the name reports are published to. |
| Approver | Start typing to search. Both individual users and user groups can be approvers; the suggestion list marks which is which. |
Each stage displays how many approvers it has. A stage can carry more than one.
Assigning a Pipeline to a Report
A report uses one pipeline at a time. Reports with no pipeline assigned show as Default, which means publishing goes directly from dev to prod with no intermediate stage.
How a Report Moves Through
- You build and save the report. That working state is dev.
- Publishing sends it to the pipeline's first stage. A new version is created if anything changed since the last publish.
- An approver on the next stage promotes it forward.
- Each promotion carries the same version onward, so what was reviewed is what ships.
Viewing Stage State
For a report with a pipeline, you can see every stage, the version currently sitting in it, and when that version arrived. Stages where you are an approver — directly or through a group — are the ones you can switch and promote.