When skipping outdated deployment jobs, how does gitlab know which jobs are deployment ones?

I was reading about deployment safety and noticed the ‘ensuring only one deployment jobs runs at a time’ which is exactly the feature I am looking for. It looks like you declare resource groups to accomplish this. I want to use the newest_first behavior, but I also want to skip older ones. The documentation says there is a CI/CD setting that you can enable that tells the pipeline to skip outdated deployment jobs. This sounds exactly what I want.

However, how does the pipeline know what jobs are deployment ones?

Does it assume the job or stage is named something particular? deploy? deployment? Or does the resource group need a special name? or is there some other special indicator I need to add to my jobs to mark them as deployment?

Here is the definition of a deployment job.

1 Like