The pipelines section defines the workflow, consisting of steps and the dependencies between them.
The basic format of each pipelines declaration is:
Tag | Description |
|---|---|
| A friendly name for the resource, unique within the project. |
| An optional section to specify environment variables and/or a |
| This is an optional step. When configured, this step will always run at the beginning of a pipeline. This is useful when you want to run some checks at the beginning of a run. Like Pipelines Steps, preRun must include at least one execution command, such as onExecute, onStart, onSuccess, onFailure, or onComplete. In addition, it can include input and output resources. pipelines:
- name: PreAndPostRuns
preRun:
execution:
onExecute:
- printenv
- echo "Executing Pre Run" |
| This is an optional step. When configured, this step will always run at the end of a pipeline. This is useful when you want to run some checks at the end of a run. Like Pipelines Steps, postRun must include at least one execution command, such as onExecute, onStart, onSuccess, onFailure, or onComplete. In addition, it can include input and output resources. pipelines:
- name: PreAndPostRuns
postRun:
execution:
onExecute:
- printenv
- echo "Executing Post Run" |
This is followed by a collection of step sections that specifies the steps to execute.
Tip
The name of the pipeline will be available in the environment variable $pipeline_name, which can be used to construct the base name for builds.