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.
Overriding Example
A "Release Manager" role could have Group1 as a member for Release1 and Group2 as a member for Release2.
Pipeline roles from the associated pipeline are displayed in a table along with configured permissions. Selecting a pipeline role’s name will open a popup displaying the role members.
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.
Tips
As a best practice, avoid assigning users directly to pipeline roles. Instead, create a group with assigned users, and assign the group to the role. This allows managing users in a centralized location, and avoids management across potentially many pipelines and releases.
Establish defaults in the role definitions of the pipeline, especially if team members are common across releases, to eliminate the need to configure the team on each and every release.
Role Permission | Description |
|---|---|
Skip Stage Execution | 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 actions on the pipeline stages in the release dashboard (e.g. Replay Stage). |
Manage Gate Execution | Whether or not this role has permission to perform actions on the pipeline stage gates in the release dashboard (e.g. Replay Gate, Skip Gate). |
Manage Step Execution | Whether or not this role has permission to perform actions on the pipeline stage steps in the release dashboard (e.g. Replay Step, Skip Step). |
Upload Execution Info | Whether or not this role has permission to upload execution information in the release dashboard (e.g. Inputs, Change Tickets). |
The detailed explanation of the above role permissions is provided below.
Assume we have pipeline roles created for different groups of users. Based on the permissions assigned to each role, an explanation with screenshots is given below.
Skip Stage Execution
This role grants permission to skip the execution of pipeline stages when creating a release snapshot. If this role is assigned, users will have the option to select specific stages to skip during the snapshot execution (refer to the screenshot below). If the role is not assigned, the option to skip stages will not be visible during snapshot creation.
Manage Stage Execution
This role grants permission to manage stage execution in the release dashboard. Users can abort or replay a stage as needed.
Manage Gate Execution
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.
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.
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.
