...
In addition to members, a role defined within a pipeline also establishes default permissions. When a release consumes the pipeline, it inherits the roles role's default permissions, but can override them for that particular role. In other words, a role may have different permissions from release to release if necessary.
...
Snapshot variables provide state for the life of a snapshot. Such state afford affords the ability to store some data as part of a step or gate in one stage, and consume it or make decisions in a later stage. One classic example is to store off a CMS ticket which was entered or created in one stage, and feed it into another stage which will use the same ticket. The pipeline defines the metadata for any snapshot variables which are available, and values can be set or retrieved using Custom Gates or Custom Steps.
To create a Snapshot Variable, click on the 
icon. Enter the required information and click Save.
| Field | Description | ||
|---|---|---|---|
| Code | The identifier which is used to access the variable from Groovy | ||
| Active | Whether the variable is active or not. Defaults to true. | ||
| Description | A description for the variable. | ||
| Data Type | The data type of the variable. Allowed types are Boolean, Integer, Double, or String. | Display Name | The display name for the variable.
Project Groups
Project Groups provide categorization tags for release content. As such, pipelines define the tags, and deploy segments of the content based on those tags. Releases consuming the pipeline can then tag its content as belonging to those groups.
...