Scheduled pipeline silently does not run when `rules` conflict with `needs`
Summary
I have a job that only runs on scheduled pipelines, using rules
. This job has a needs
dependency on another job. That job does not run on scheduled pipelines (also using rules
).
This is a bug in my CI config, and I would like to be notified about it (somehow). Instead, when I attempt to manually run the scheduled pipeline, I get the usual notice to check the Pipelines listing... which does not contain the pipeline I just triggered.
Steps to reproduce
- Configure CI job A that does not run on scheduled pipelines.
- Configure CI job B that only runs on scheduled pipelines.
- Configure B to depend on A using
needs
. - Configure a schedule that runs your pipeline.
- Trigger the scheduled pipeline manually.
Example Project
https://gitlab.com/brett.higgins/scheduled-pipeline-bug-demo
What is the current bug behavior?
The page says the pipeline started, but the pipeline did not start. (See screencap)
What is the expected correct behavior?
Since the pipeline cannot run any jobs, an error message should appear saying that nothing could be scheduled.
Relevant logs and/or screenshots
Screen_Recording_2021-03-20_at_1.55.24_PM
Output of checks
This bug happens on GitLab.com