Skip to main content

Release changes that have not been tested

With the merge lane on, changes merged after the lane's newest tested commit wait for tests. They are not listed on the Release step. When one of them can't wait, a whole Release ships it now, without the full tests.

Who can do this​

Whoever may release into the next stage and edit the project's pipeline: the same right as overriding a freeze. For anyone else, Release ships the newest tested commit only, and the rest ship in a later release, once tested.

What it ships​

A Release with nothing ticked ships everything waiting on the stage, the newest commit included. Ticking rows ships only those tested changes. Approvals, a change ticket and the rest of the step's rules still hold it like any release.

While the step is closed until the stage before it passes its checks, Release stays greyed out.

Release untested changes​

  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.
  3. Tick no rows.
  4. If the step asks for a change ticket, enter it in Ticket first. Until then Release stays greyed out.
  5. Select Release N. Its number counts the untested changes too. Hover the button for how many are not tested yet. It sends at once, with no confirmation. The Audit page records it with No reason given.
  6. Watch the Release step and the next stage's block. The list turns into the release's progress, as for any release.

If it fails, the bar shows Run when the deploy has a page. To try again, select Release once more, as in Release to production.