Schedule a deploy
A release normally starts the moment you select Release. To have it start later, such as outside working hours, give it a date and time in When. The release then waits, scheduled, and starts by itself at that time.
Who can do this: whoever may release into the next stage: anyone with edit access to the project, unless its pipeline names who may press Release.
Schedule a releaseโ
-
In the sidebar, select the project. The stage strip sits under the top line.
-
Select the Release step between Dev and Production. The list of what waits opens, with the release actions above it.
-
Tick no task to ship everything, or tick only the tasks that should ship (Ship only some changes in a release).
-
Select Now, with the clock, beside Release N. It turns into a date and time field.

-
Pick the date and time, in your own time zone. Release N stays greyed out until you pick one.
-
Select Release N. It is scheduled at once, with no confirmation. The row shows a Scheduled chip with the time.
To go back to releasing now before you press Release N, select the clock inside the field.
While it waitsโ
- The open release reads Scheduled and its time on the Release step.
- Cancel withdraws it before it starts.
- When the time comes, the release still waits for anything else that holds the step, such as approvals, allowed hours or a freeze. Hover the step's chip to see why (Release to production).
During a freeze, When opens on its own at the freeze's end, and the clock can't switch it back to now. A release refused because a freeze covers the time you picked says Frozen until and the time; pick a later one.
Relatedโ
- Release now, approvals and failures: Release to production.
- Hold a step to set days and hours every time: Limit when a step runs.
- Freezes and every other step rule: Set up a project's pipeline.