I am trying to utilize the “Prevent outdated deployment jobs” feature. For testing purposes I have created this simple job:
test-restriction: stage: deploy environment: release resource_group: build-image-release script: - sleep 40 - echo "I have done nothing"
The resource group is configured so that the newest pipeline runs first. What I expected to happen was, that all older jobs are cancelled. However this is not the case, as seen in the screenshot:
As you can see deployment jobs with different sha and lower ID are executed after a deployment job with higher ID had finished.
For manual jobs the feature seems to work:
I’m using a self-managed Gitlab.
- GitLab: 15.10.1-ee
- Runner: 15.9.1
Has anyone else experienced problems with this feature?