Customize "Skip CI" message at the Job level.
Description
The [ci skip] is good to skip any commit. But we have a use case for refs that should not trigger builds for only certain jobs, but do for others. We want to customize the skip message per job on the gitlab yaml so that only that job is skipped for that message.
For example we upgrade certain dependencies and don't wan't a "deploy" stage job to be triggered, but we do want the "build" stage job to be triggered by it that packages artifacts and run some tests. This is not currently possible if the [ci skip] is included in the commit message. We can work around it though this is tedious for certain reasons.
Use Cases/Examples
- We update dependencies and want to merge but not deploy the code again with only that change
- IaC pipeline to update a terraform module without running a deploy
- Emergency patches to skip integration testing
Proposal
Add a variable at the job level indicating the skip message format.
Questions to answer
- What if an org does not want a job to be skippable?
- What if only owners could do this?
Security/Access
Measures of Success
After launching this feature we'd expect to see an increase in usage of [skip ci] messages of x%