Skip to main content

Limit when a step runs

Two timing rules hold a pipeline step back until the moment suits you:

  • Wait after arrival keeps work in a stage for a set time before the next step may run, so a change can soak on Dev before it goes to Production.
  • Allowed hours lets the step run only on chosen days, between two times, in one time zone. Outside them the step waits for the next allowed hour.

Either rule or both may be set. They hold a step that runs By itself and one someone presses alike.

Who can do this: anyone who may edit the project. Others see the settings but can't change them.

Plan: timing is set in a project's custom pipeline, under Settings › CI Pipeline, which shows only where the organization's plan includes Custom pipelines.

Set a wait after arrival​

  1. In the sidebar, select Directory, then the Projects tab, and select the project's name.
  2. In Settings, select CI Pipeline. Under Steps, select the step to hold, such as Release from Dev to Production. Its settings open.
  3. Under Timing, type a number in Wait after arrival and pick its unit: minutes, hours or days. The longest wait is 30 days. Empty means no wait.
  4. Select Save at the foot of the tab.

The step's summary under Steps now ends with the wait, such as Wait 1h.

Set allowed hours​

  1. Open the same step's settings, as in steps 1 and 2 above.
  2. Under Timing, tick Allowed hours. It starts at Mon to Fri, 09:00 to 17:00, in your browser's time zone.
  3. Under Days, tick each day the step may run.
  4. Set From and To. A To earlier than From runs overnight, such as 22:00 to 06:00.
  5. Pick the Time zone the hours are in.
  6. Select Save.

The step's summary now shows the window, such as Mon–Fri 09:00–17:00. To drop the rule, untick Allowed hours and select Save.

See why a step waits​

On the Tasks page, a held step shows a chip naming the first thing that holds it: Soak 42m during a wait, or Off hours outside the allowed hours. Hover or tap it for Ready in (the wait left) or Next allowed (the next allowed hour, such as Mon 09:00 (Europe/Berlin)). The full list of reasons is in Release to production.

To hold every release for a planned window, such as a holiday, use a freeze instead; see Set up a project's pipeline.