...
A Team defines a set of roles which will participate during execution of the pipeline. Roles assigned to the pipeline may then be used within the defined gates and steps (i.e. an approval step). A role contains default members, which can be FlexDeploy Groups, FlexDeploy Users, or email addresses (used for notifications only). A release which consumes the pipeline inherits the roles and default members from the pipeline, and can override those members. For example, the Release Manager members can be different across releases.
| Tip | ||
|---|---|---|
| ||
Groups may not be assigned directly to gates or steps. Instead, you must create a pipeline role and assign the appropriate group as a member. 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. |
In addition to members, a role defined within a pipeline also establishes default permissions. When a release consumes the pipeline, it inherits the roles default permissions, but can override them for that particular role.
Properties
Project Groups
Referenced By
...