Skip to main content

Ship only some changes in a release

A release normally moves everything waiting on a stage to the next one. When some of it isn't ready, tick only what should ship: Jaah copies just those changes onto the next stage's branch, oldest first, and the rest keep waiting.

Who can do this: anyone who may release the project, as for any release (Release to production).

Pick what ships​

  1. In the sidebar, select Tasks, then the project. The stage strip sits under the top line.

  2. Select the Release step between the two stages, such as Dev and Production. The list shows what waits, none ticked, and the row above it reads, for example, 17/17 shipping: with nothing ticked, everything ships.

    The row above the Release list with nothing ticked: 17/17 shipping, cost, tokens, oldest, Now and Release 17

  3. Tick each task that should ship. A change with no task has its own line and its own tick. The tick at the start of the row, Select all, ticks or clears every row.

  4. Check the row. It now counts only what you ticked, such as 1/17 shipping, and its cost, tokens and oldest age are the ticked tasks' own. Release N names the same number.

    The same row with one task ticked: 1/17 shipping and Release 1

  5. Leave When at Now, or select the clock to pick a time.

  6. Select Release N. It sends at once, with no confirmation. The list turns into the release's progress, as for any release.

The tasks you didn't tick stay on the source stage and wait for the next release.

What ships beside the ticked rows​

With nothing ticked, the row can show two more figures, and both ship too:

  • +N after the count: changes on the stage that this list doesn't show, because a filter hides their task or it sits elsewhere. Hover it for how many.
  • +N for commits with no task. Hover it for how many.

Once you tick anything, neither ships: a pick ships its own changes alone.

With the merge lane on, a release of everything ships the lane's newest tested commit. Changes merged after it are not listed and can't be ticked. A pick ships only the tested changes you ticked.

If you can edit the pipeline, a release with nothing ticked ships those changes too, without the full tests. For anyone else they ship in a later release, once tested (Use the merge lane). See Release changes that have not been tested.

When Release won't go​

  • Release stays on the bar even when it can't send anything. Hover it for why: nothing new, nothing tested yet, or you can't release to that stage.
  • Release greys out when everything you ticked has already shipped in another release. Tick again from what still waits.
  • A pick can't join a release already open into the same stage. Wait for that one to finish, or cancel it, then release your pick.
  • Approvals, freezes and other waits hold a pick like any release: the chip above the list says why (Release to production › Why a step waits).