Versions Compared

Old Version 44

changes.mady.by.user Erick Jones

Saved on

compared with

New Version 45

changes.mady.by.user Karl Henselin

Saved on

Key

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

To create a new pipeline, navigate to the Search Pipelines screen using the Piplelines menu, and click on the Create button.  To edit an existing pipeline, click on the Pipeline Name column of the target pipeline in the search results, or select the row and click the Edit button.

...


Field

Description

Name

The name of the pipeline.

Updated On

The user who last updated the pipeline verson (read-only).

Updated By

The last update date/time of the pipeline version (read-only).
 

Definition


The Definition tab provides the definition of the pipeline stages, and their steps and gates.  Changes to the pipeline, like a workflow, are versioned so that changes can be published to consumers, or previous versions can be reverted.

Field

Description

Description

A free-form description of the pipeline version.


...

Note

Any pipeline version which is active, or has ever been active, is locked from future edits.  You must make a copy in order to make further changes.

...

Team

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.

...

Click the  button to save the changes to the role (be sure to also save the pipeline, or changes will be lost), or  to revert any unsaved changes.

 

Properties

Pipeline Properties are used to decorate a release with some context.  Values for the properties are provided on each release, and may be used in various groovy scripts within the pipeline definition.  For example, only execute a particular step in the pipeline if the "Release Type" is "Security".

...

Field

Description

Active

Indicates whether the pipeline property is active.  Inactive properties will not appear on the release.
CodeA code for the property, as appropriate for variables within Groovy or Shell scripts.  (e.g. no spaces or special characters other than underscore.)

Description

A meaningful description for the property.  
Data TypeThe data type for this property. Valid types are Boolean, Double, Integer, String.
SubtypeNot currently used.
Default ValueA default value to assign to the property if not specified on the release.
RowsDefines the height of the component to display when capturing the value from the user.
ColumnsDefines the length of the component to display when capturing the value from the user.
Display NameA meaningful name for the property used for display.
List Data

A list of valid values for the property.  Optional, and only applicable for String data type.  Allowed formats:

  • Value1,Value2,Value3
  • Key1,Value1##Key2,Value2##Key3,Value3       (e.g. Key1 will be what is displayed, Value1 will be the actual value when selected)
  • ,Value1,Value2       (e.g. Note comma in the front - will result in empty item in list)
  • ##,Key2,Value2       (e.g. Empty item in list)
EncryptedWhether or not to encrypt the value, not display on screen or in the logs.  Only applicable for String data type.
MultiselectWhether multiple values can be selected from the List Data.  Only applicable for String data type, and when List Data is provided.
LengthThe maximum allowed length of the property value.  Optional, and only applicable for String data type.
RequiredWhether or not a value is required for this property.
Min ValueMinimum allowed value.  Optional, and only applicable for Integer and Double data types.
Max ValueMaximum allowed value.  Optional, and only applicable for Integer and Double data types.
Validator1

Optional Groovy Script to validate provided value.  The script should return true if the value is valid, and false otherwise.  The user specified value is available to the script in the Value variable.  If not valid, the ValidationMessage is displayed to the user.

For example,

Code Block
languagegroovy
titleExample
if ("BAD".equals(Value)) {ValidationMessage="Bad value!!"; return false;} else {return true;}


Validator2Optional Groovy Script to validate provided value.  See Validator1.
Validator3Optional Groovy Script to validate provided value.  See Validator1.
Validator4Optional Groovy Script to validate provided value.  See Validator1.
Validator5Optional Groovy Script to validate provided value.  See Validator1.


Click the  button to save the changes to the property (be sure to also save the pipeline, or changes will be lost), or  to revert any unsaved changes.

 

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.

...

To delete a project group, click on the  icon for the project group you wish to remove.

 

Referenced By

Identifies the Releases which are referencing this pipeline.

...