Stages
Learn about stages pipelines.
A stages pipelines are designed to parallelize one-to-many sets of step tasks.
By design all of the stages will run at the same time unless the user uses a needs: YAML key to control the flow of stage executions (see example).
Stages will also stop executing their steps if the build fails as a whole, by default. In other words, if stage 1 fails, the steps that have yet to execute in stage 2 will be skipped. The user can declare independent: true for any stage to change this behavior.
These pipelines do not have a minimum defined length and will always execute steps within a stage in the order defined. Stages always run on the same host so it’s important to take into consideration the size of the worker running your builds.
In this pipeline both stages trigger at the same time.
Both steps are pulling a Alpine Linux image from Docker Hub and executing echo statements.
See it in action with examples!
You can learn more about stage orchestration here!
version: "1"
# In this pipeline, commands are executed inside the container as the Entrypoint.
# If any command returns a non-zero exit code, the pipeline fails and exits.
stages:
greeting:
steps:
- name: Greeting
image: alpine
commands:
- echo "Hello, World"
welcome:
steps:
- name: Welcome
image: alpine
commands:
- echo "Welcome to the Vela docs"
goodbye:
# will wait for greeting and welcome to finish
needs: [greeting, welcome]
steps:
- name: Goodbye
image: alpine
commands:
- echo "Goodbye, World"
Note:
Be aware thatneeds: references stages by their name, which can be overridden by the name key in the stage definition.$ vela exec pipeline
...
[stage: greeting][step: Greeting] $ echo "Hello, World"
[stage: greeting][step: Greeting] Hello, World
[stage: welcome][step: Welcome] $ echo "Welcome to the Vela docs"
[stage: welcome][step: Welcome] Welcome to the Vela docs
[stage: goodbye][step: Goodbye] $ echo "Goodbye, World"
[stage: goodbye][step: Goodbye] Goodbye, World