See which changes are still in testing
With the merge lane on, a release ships the lane's newest tested commit. Changes merged after it are still being tested. The Pipeline view lists them with the rest, marked with a flask in a turning ring instead of the done tick, so the count on Release matches the rows you see.
Who can do this: anyone who can see the project's tasks. The mark shows only on a project with the merge lane on: see Use the merge lane.
- In the sidebar, select Tasks, then the project in the Projects tree. Select the Pipeline tab at the top of the page.
- Select the stage the lane tests, such as Dev, in the stage strip. Its finished changes are listed with a green tick.
- Look for rows that lead with a flask in a turning ring. Hover the flask: it reads Testing. Those changes merged after the newest tested commit. A commit with no task carries the same mark on its own line.
- Select the Release step after the stage. The list shows the tested changes first, each with a tick box, then the changes still in testing, with the flask and no tick box.
- Read the count above the list, such as 11/24 shipping, and the number on Release. Both count what this
release would ship:
- a whole release ships the tested changes. If you can edit the pipeline, it ships the changes still in testing too, without the full tests: see Release changes that have not been tested;
- a pick ships only the tested changes you ticked. A change still in testing can't be ticked.
- Wait for the flask to turn into the done tick. Once the lane has tested a change, it ships in the next release like any other.
In the Production section, Next release marks its changes still in testing the same way: see Follow a release on the pipeline view.
Related
- Ship only some changes in a release: tick what goes out and leave the rest waiting.
- Find out why the merge lane is stuck: when changes stay in testing too long.
- Switch between the tasks and pipeline views: the Tasks page's tabs.