Scheduled pipeline triggers wrong job
Summary
Scheduled pipeline triggers wrong job(s)
Steps to reproduce
- Create two stages:
monitoring
andtest
- Create job in
monitoring
stage that should run only for scheduled pipelines - Create job in
test
stage that should run only formaster
branch
Example Project
https://gitlab.com/kromol/test-ci-scheduled-pipeline
What is the current bug behavior?
Triggering scheduled pipeline both jobs are being executed, however according to the only/except docs it should not do it, because by default:
If a job does not have an only rule, only: ['branches', 'tags'] is set by default. If it doesn’t have an except rule, it is empty.
What is the expected correct behavior?
Scheduled pipeline should trigger only jobs which are supposed to be triggered by scheduled pipeline explicitly
Relevant logs and/or screenshots
kromol/test-ci-scheduled-pipeline@6ed08264 - example of triggered by scheduled pipeline.
Output of checks
This bug happens on GitLab.com
Edited by Jason Yavorska