Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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, along with and it also allows for overriding the members. Overriding role members by release allows for different responsibilities for specific releases.

Tip

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 associated configured permissions. Selecting a pipeline role’s name will open a popup displaying the role members. 

...

Tip

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

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 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).