Don't run coverage stage jobs when only docs are being updated
What does this MR do?
Fixes a regression in CI Pipeline configuration for this project, introduced in !1060 (merged).
Why was this MR needed?
While refactoring CI Pipeline configuration in !1060 (merged) I've removed the <<: *except_docs part from coverage job's definitions, wanting to add this to the base template that I've created. But finally I've forgot to add it there. This causes now all docs-only Pipelines to fail, because coverage jobs are started but there is no tests artifacts that they can work on.
This MR resolves this problem.
Are there points in the code the reviewer needs to double check?
Does this MR meet the acceptance criteria?
-
Documentation created/updated -
Added tests for this feature/bug -
In case of conflicts with master- branch was rebased