Skip CI jobs for docs to enhance productivity
The problem
For every new doc, or for changes in docs, currently we need to build the entire application (CE, EE, Omnibus, Runners).
AFAIK, we don't need to run all the CI jobs for CE and EE (omnibus and runner) for documentation. Isn't there a way to skip some of them? Waiting for 1h to see if our MR is good to go (jobs passed) is very distracting, and keeps us from moving on to our next task. And it's very common to see that our pipeline has failed bc of "the server took to long to respond" or receiving a 502, or something.rb
didn't pass.
We are only creating/updating plain markdown, there should be a way to make pipelines faster for our docs.
Examples of jobs failing that don't have anything to do with our changes in markdown files:
- https://gitlab.com/gitlab-org/gitlab-ce/builds/14186306
- https://gitlab.com/gitlab-org/gitlab-ee/builds/14186810
- https://gitlab.com/gitlab-org/gitlab-ee/builds/14186808
And there's a lot more that I've seen recently.
The solution
Suggestions:
- Somehow skip jobs related to changes in files in the
doc
folder, or - Add an
except
component to branches nameddocs-*
to each job we want to skip
@DouweM @smcgivern could you please look into this?
cc/ @seanpackham @axil @JobV