1.11 Steps

Each job has a single build plan configured as job.plan. A build plan is a recipe for what to run when a build of the job is created.

A build plan is a sequence of steps:

• the task step runs a task

• the get step fetches a resource

• the put step updates a resource

• the set_pipeline step configures a pipeline

• the load_var step loads a value into a local var

• the in_parallel step runs steps in parallel

• the do step runs steps in sequence

• the across step modifier runs a step multiple times; once for each combination of variable values

• the try step attempts to run a step and succeeds even if the step fails

When a new version is available for a get step with trigger: true configured, a new build of the job will be created from the build plan.

When viewing the job in the pipeline, resources that are used as get steps appear as inputs, and resources that are used in put steps appear as outputs. Jobs are rendered downstream of any jobs they reference in passed constraints, connected by the resource.

If any step in the build plan fails, the build will fail and subsequent steps will not be executed. Additional steps may be configured to run after failure by configuring on_failure or ensure (or the job equivalents, job.on_failure and job.ensure).