Skip to content

fix: ci stages not correctly sorted

Tomas Vik requested to merge 444-sort-ci-stages into main

We get the CI stage order from the order of jobs. Before this MR, that order was dictated from the API and it was the exact opposite of what we need. This MR sorts the jobs by id in ascending order. That ensures that jobs from earlier stages are processed first and the final order of the stages is from early to late stages.

before after
pipeline_item_model_test_ts___gitlab-vscode-extension Extension_Development_Host_-_token_service_ts___gitlab-vscode-extension-TEST

Related to #444 (closed)

Edited by Tomas Vik

Merge request reports