Page Comparison

Name

The name of the step.

Description

An optional description for the step.

Project

The name of the project in the snapshot (or release for Utility projects) to execute tests for (according to its strategy).  This project must be in the snapshot/release, or the step will fail.

Package

@Since 7.0.0.2 - The name of a package in the selected project to execute tests for (according to its strategy). This package must be in the snapshot/release, or the step will fail.

Test Name

Identifies which test to execute.  If not specified, all

tests will be executed. Use comma-separated test names, or supply a regular expression to match one or more test names.

Optionally, use a Groovy expression to make this field dynamic based on some contextual value (e.g. a property defined on the pipeline, and specified on the release).

@Since 7.0.0.1 - Suggestions will be given once a project is selected based off that project’s test configuration YAML. If both test name and test tag are specified we will consider an intersection between them.

Tags

@Since 7.0.0.1 - Filters for tests to execute with at least one matching tag. If not specified, all tests will be executed. Use comma-separated tags, or supply a regular expression to match one or more tests' tags. Suggestions will be given once a project is selected based off that project’s test configuration YAML.

Optionally, use a Groovy expression to make this field dynamic based on some contextual value (e.g. a property defined on the pipeline, and specified on the release).

Precondition

An optional Groovy script which determines whether the gate or step is applicable during execution. The script has access to variables and methods listed in Pipeline Groovy Variables and Methods. You can find these variables and methods

while using the Groovy Editor.

The script must return true if the

step is applicable, or false otherwise.  If no script is provided, the default is to return true (applicable).

On Error

Continue

If checked, any failure will be ignored, and the pipeline execution will continue.

Notify Pipeline Role

Selects one or more roles from the pipeline definition to notify in case of error.  Default role members are defined on the pipeline, and

optionally overridden for each release. Optionally, use a Groovy expression to make this field dynamic based on some contextual value (e.g.

a property defined on the pipeline, and specified on the release).

When using a role script you can dynamically return a key/value pair. For example return [type: 'groupName', value: 'FD Administrators']. Supported types are roleId, roleName, groupId, and groupName. You can return Map with single key/value pair or list of such single key/value maps.