Stage types

A Blank canvas stage starts empty so you can add any combination of step types manually.

A Blank canvas stage starts with no pre-configured sections. Use it when your stage does not fit neatly into a Build or Deploy pattern, for example, a stage that runs approval workflows, executes custom scripts, calls external APIs, or combines actions from multiple modules.

Starting with a blank canvas does not limit what you can do. You can add build steps, deployment steps, or any combination of step types; there are no restrictions on which steps are available or how you use them.

What you will learn

• When to use a Blank canvas stage instead of a typed starting point like Build or Deploy

• What configuration sections are available on a blank canvas stage

• How to add any mix of step types to a blank canvas stage

When to use blank canvas

• Your stage mixes build and deploy actions and you do not want a type-specific starting layout

• You are building an approval, notification, or governance gate between other stages

• You want full control over which step types and configurations to add without any scaffolding

• You are assembling a stage from a set of custom script or plugin steps

What you configure

A blank canvas stage has no pre-filled sections. You configure everything from scratch:

Section	What you configure
Steps	Add steps manually from the step library: run scripts, approvals, HTTP calls, plugins, and more
Inputs & outputs	Define any stage-level inputs, outputs, and environment variables the steps depend on
Execution controls	Set failure strategy, looping strategy, conditional execution, and timeout
Runtime Environment	Choose the platform, runtime type, and any shared paths

Next steps

• Go to Steps overview to review the full list of step types you can add to any stage.

• Go to Stage overview to understand how stages work and how to add them to a pipeline.