An alphanumeric string (underscores are permitted) that identifies the step. The name should be chosen to accurately describe what the step does, e.g.
prov_test_env to represent a job that provisions a test environment. Names of steps must be unique within a pipeline.
PowerShell for this step type.
Specifies all optional configuration selections for the step's execution environment.
Description of usage
|Label that controls affinity to a Node. All the steps with the same affinityGroup will be executed on the same node. This will allow sharing state between the steps. An example is having the same affinityGroup for DockerBuild and DockerPush steps in a Pipeline so that Image being built in the DockerBuild step can be used to published in the DockerPush step||Optional|
Controls the priority of a step when there are parallel steps in a pipeline or multiple pipelines executing. It determines which step will run first across all steps that could run if there were no constraints on the number of steps running. Steps with a lower number will run before steps with higher numbers. For example, priority 10 will run before priority 100. The default priority is 9999.
Priority does not apply to steps that are still waiting for an input to complete or configured to run in a node pool with no available nodes. Also, if there are two steps ready to run and only one available node, the one with the lower priority number runs first, regardless of which pipeline each step belongs to.
|Time limit, in the number of seconds, for the step to complete. If the step does not complete in the given time limit, the step will be forced to a completion state of failed.||Optional|
|Assigns the node pool on which the step executes. If node pool isn't specified, a step will execute on the default node pool. See here to learn more about node pools.||Optional|
Specifies that the step must execute in chronological order, to ensure receipt of all state updates from preceding steps.
|Assigns any environment variables and their values in key:value format. All environment variables assigned within a step definition are active only for the scope of the execution of that step. Variables will be available in global scope and in the |
If the following variables are set, they will be used:
|A collection of integrations that will be used by this step. Integrations can be used directly in step without a resource.||Optional|
|A collection of named steps whose completion will trigger execution of this step.||Optional|
A collection of named resources that will be used by this step as inputs.
By default, changes to these named resources will trigger execution of this step. This can be changed by declaring
A collection of named resources that will be generated or changed by this step.
|Specifies the runtime for the execution node.||Optional|
Declare sets of shell command sequences to perform for different execution phases:
|Tag||Description of usage||Required/Optional|
|Commands to execute in advance of ||Optional|
|Main commands to execute for the step||Optional|
|Commands to execute on successful completion of ||Optional|
|Commands to execute on failed completion of ||Optional|
|Commands to execute on any completion of ||Optional|
This is an example of how to use the PowerShell step to perform a build activity.