Stages define the list of pipeline stages, with multiple stages executed sequentially in the order declared. Pipeline stages are used to aggregate a group of tasks related to specific objectives, corresponding to specific phases in the development process, such as code check, build, test, and more. ## **YAML example** ```YAML stages: - stage: build displayName: build tasks: - task: cmd-exec displayName: command timeout: 2h resourcesPolicy: all steps: - step: exec-cmd displayName: command component: exec@1.0.0 inputs: cmd: echo hello shell: BASH resources: limits: cpu: 1C memory: 2Gi final: - task: task-c1 displayName: clear timeout: 2h resourcesPolicy: all resources: limits: cpu: 1C memory: 2Gi steps: - step: step-c2 displayName: clear component: exec@1.0.0 inputs: Shell: Bash cmd: echo "cleaning up..." ``` ## Parameter |**Parameter** |Required |**Description** | |---|---|---| |stages.stage |Yes |Stage ID. ID must meet the following requirements:

* Can only contain lowercase letters (a–z), digits (0–9), and hyphens (\-).

* Must start with a lowercase letter or digit.

* Must end with a lowercase letter or digit.

* Length must be 1–40 characters. | |stages.displayName |No |Stage display name, shown in the pipeline console. The displayName length must be 1–50 characters. | |stages.tasks |Yes |The task collection under the stage must include at least 1 item. For parameter details, see [Pipeline tasks](https://www.volcengine.com/docs/6461/2371384). | ## Final Stage The final stage is used to execute cleanup and wrap\-up tasks after the pipeline ends. Caution: After enabling, note the following: * You can add multiple tasks to the final stage, but only parallel execution is supported between tasks. * Regardless of whether preceding tasks succeed or fail, tasks in the final stage will always execute. ## Cross\-stage artifact reference To reference outputs generated by upstream steps, please use the following unified format expression. For parameter details, see [Step list](https://www.volcengine.com/docs/6461/2384021). `$(stages..tasks..outputs._)` * : Stage ID. * : Task ID. * : Artifact name, defined by each step, for example imageOutput, artifactOutput, and more. * : Step ID.

Code Pipeline