Skip to main content

Merge tasks through a freeze

A freeze on a project's pipeline can hold its Merge step, so finished tasks wait instead of merging into the integration branch. When one change can't wait, such as an urgent fix, you can override the freeze for the tasks you pick. You give a reason, the tasks merge at once, and the freeze stays on for everything else.

Who can do this: someone who may press the Merge step and edit the project's pipeline. Without both, the bar doesn't offer the override.

  1. In the sidebar, select Tasks, then the project, then the Pipeline tab.

  2. Find the stage before the Merge step, on the stage strip or by scrolling to its section. A step a freeze holds shows a chip such as Frozen; hover it for every reason.

    The stage strip: Ideas 1, Building 4, Dev 17 and Production 0, with the Merge step between Building and Dev. No freeze holds it here

  3. Tick the tasks to merge: select ⋯ at the end of a row, then Select. Tick tasks from that one stage only.

  4. In the bar at the bottom, select Override freeze.

  5. The dialog is titled Override freeze “Name” with the freeze's name, or Override Freeze now when someone switched on Freeze now. It says how many tasks run now, such as Merge 2 tasks runs now. Recorded on the Audit page.

  6. In Reason, say why this can't wait. It needs at least 10 characters.

  7. Select Override and merge. The bar reports the result, such as Merging 2. If no task could be pressed, the dialog says so and stays open.

The override, with your name and reason, is recorded on the Audit page. The freeze keeps holding every other task. To stop a freeze for everyone, end it in the project's pipeline settings instead.

The capture shows the strip with no freeze active: the organization it was taken in had no freeze holding a Merge step, so Override freeze and its dialog could not be photographed.