...
The Roles section in the pipeline defines a set of roles that will participate during the execution of the pipeline. Roles assigned to the pipeline may then be used within the defined gates and steps (e.g. an approval step). A role contains default members, which can be FlexDeploy Groups, FlexDeploy Users, or email addresses (used for notifications only). A release that 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 |
|---|
Tips Pipeline role is generally used in gate or step configurations, but FlexDeploy 7.0 allows use of Groups directly in gate or step as well. Hence creation of pipeline role is optional. If you need to provide specific permissions for skip, replay, abort, override etc. then pipeline role is required. 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.
|
...