Invalid gitlab-ci.yaml ignores [ci-skip]
Problem to solve
When a user has an invalid .gitlab-ci.yml
it will fail a commit's pipeline, even when [ci skip]
is specified in the commit message. There is a lack of visibility into the ci_skip of the commit and pipelines that introduced the invalid configuration when ci_skip is used.
Example Flow:
commit the following file with [ci skip]
in the commit message:
# .gitlab-ci.yml
stages:
- test
build:
stage: build
script: echo "hello"
matthias.vandemeent/test-ci-results@a5d1eea5
-
A notification "your pipeline failed", and the commit gets a failed pipeline
-
yaml invalid
is given higher priority than the[ci skip]
Desired user experience
- There is no notification "your pipeline failed", the commit has
skipped
orwarning
status. - Visibility into when invalid syntax has been introduced with ci_skip
Proposal
[ci skip] should always behave in the same way regardless of the contents of the commit and the validity of the pipeline syntax
Edited by Veethika Mishra