The pipeline referenced by a release optionally defines a set of pipeline roles with default members. The Roles tab allows viewing the roles and their members, and it also allows for overriding the members. Overriding role members by release allows for different responsibilities for specific releases.
| Tip |
|---|
Overriding ExampleA "Release ManagerTechnical Leads" role could have Group1 as a member for Release1 and Group2 as a member for Release2. |
...
To override the members for the release, select the switch at the top right next to Override Members. Now, when opening a role’s popup, you can add and remove groups and users from the role. Multiple email recipients (used for notification only) can be specified by separating with either a semi-colon or comma. To revert the members of a role to the defaults defined on the pipeline, unselect the switch on top next to Override Members. Permissions associated with a role can only be modified on the pipeline. Remember to click Save to save your changes.
...
| Tip |
|---|
Tips
|
Role Permission | Description |
|---|---|
Skip Stage Execution |
Whether or not this role has permission to skip the execution of pipeline stages when creating a release snapshot. | |
Manage Stage Execution | Whether or not this role has permission to perform Replay Stage, Abort Stage actions on the pipeline stages in the release dashboard |
. | |
Manage Gate Execution | Whether or not this role has permission to perform Replay Gate, Skip Gate, Abort Gate actions on the pipeline stage gates in the release dashboard |
. Test and Scan Gate can also be skipped if user is member of gate override role without this permission. Schedule Gate can only be overridden to run immediately only if user is part of gate override role. | |
Manage Step Execution | Whether or not this role has permission to perform Replay Gate, Skip Gate, Abort Gate actions on the pipeline stage steps in the release dashboard |
. Schedule Step can only be overridden to run immediately only if user is part of step override role. Wait Step can only be overridden to run immediately if user has this permission. | |
Upload Execution Info | Whether or not this role has permission to upload execution information in the release dashboard (e.g. Inputs, Change Tickets, Deploy Overrides etc.). |
The detailed explanation of the above role permissions is provided below.
...
This role grants permission to perform actions on pipeline stage gates in the release dashboard. Users can replay or skip a gate if it has been rejected, failed, or aborted. Additionally, users can override a gate if it is waiting on a scheduled gate.
...
User can also abort gate.
...
Manage Step Execution
This role grants permission to perform actions on pipeline stage steps in the release dashboard. Users can replay or skip a step if it has been rejected, failed, or aborted. Additionally, users can override a step if it is waiting on a scheduled step.
...
User can also abort a step.
...
Upload Execution Info
This role grants permission to upload execution information in the release dashboard during stage execution. You should see a paperclip icon on each stage. Clicking on it will open the "Stage Execution Info" popup, where you can add a Change Ticket number, override the Target Group, force/skip/override the deployment execution, and add Workflow inputs. Once you upload the details, the stage execution will use this information during the execution.
...