This topic lists tags that can be used with SignReleaseBundle Pipeline steps. For more information on SignReleaseBundle Pipeline steps, see SignReleaseBundle.
name
An alphanumeric string (underscores are permitted) that identifies the step.
type
Must be SignReleaseBundle 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 a ReleaseBundleresource whose | Required |
| Must specify a ReleaseBundleresource. This ReleaseBundle is updated with the | Required |
There is no additional configuration required.
Tags derived from Bash
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.
GPG Signing Key Passphrase
When your Distribution release bundle GPG signing keyis passphrase protected, remember to provide the GPG Signing Key Passphrase when creating/updating your Distribution Integration.
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.