This topic lists tags that can be used with CreateReleaseBundle Pipeline steps. For more information about CreateReleaseBundle Pipeline steps, see CreateReleaseBundle.
name
An alphanumeric string (underscores are permitted) that identifies the step.
type
Must be CreateReleaseBundle
for this step type.
configuration
Specifies all configuration selections for the step's execution environment. This step inherits the Bash/ PowerShell step configuration tags, including these pertinenttags:
Tag | Description of usage | Required/Optional |
---|---|---|
| Must specify either a named BuildInfo resource(s) or an Aql resource. CreateReleaseBundle step does not accept other input resources. If BuildInfo | Required |
| Must specify a ReleaseBundleresource. The | Required |
In addition, these tags can be defined to support the step's native operation:
Note
All native steps derive from the Bash step. This means that all steps share the same base set of tags from Bash, while native steps have their own additional tags as well that support the step's particular function. So it's important to be familiar with the Bash step definition, since it's the core of the definition of all other steps.
Tag | Description of usage | Required/Optional |
---|---|---|
| An alphanumeric name for the release bundle. | Required |
| Version string for the release bundle. | Required |
| When set to Default is true. | Optional |
| Specifies whether the release bundle version will be signed as part of this step. Default is false. GPG Signing Key PassphraseWhen configuring | Optional |
| Description of the release bundle. | Optional |
| Describes the release notes for the release bundle version.
| Optional |
| Fail the step if one of the signatures of the BuildInfo input resource artifacts cannot be verified. Default is | Optional ( Signed Pipelines must be enabled) |
execution
Declares collections of shell command sequences to perform for pre- and post-execution phases:
Tag | Description of usage | Required/Optional |
---|---|---|
| Commands to execute in advance of the native operation | Optional |
| Commands to execute on successful completion | Optional |
| Commands to execute on failed completion | Optional |
| Commands to execute on any completion | Optional |
The actions performed for the onExecute
phase are inherent to this step type and may not be overridden.
Note
onExecute
, onStart
, onSuccess
, onFailure
, and onComplete
are reserved keywords. Using these keywords in any other context in your execution scripts can cause unexpected behavior.