Pipeline error thrown when no jobs should run involving only:changes
When no jobs should run in a pipeline and at least one of those jobs' conditions involve an only/changes that is false, the UI incorrectly throws an error instead of not triggering a pipeline.
Note: This is a big blocker for the customer because they need to have "Only allow merge requests to be merged if pipeline succeeds" setting on
Steps to reproduce
- Create or edit a
.gitlab-ci.ymlwith at least 1 job.
- If it's a new branch, make a subsequent commit.
- Ensure that the commit makes it so that no jobs should run and at least one job involves only/changes
Originally reported by customer (internal): https://gitlab.zendesk.com/agent/tickets/116657
What is the current bug behavior?
Attempts to trigger a pipeline and throws an error.
Could not retrieve the pipeline status. For troubleshooting steps, read the documentation.
What is the expected correct behavior?
Should not attempt to trigger a pipeline, similar to: https://gitlab.com/cynthia/ci-only/merge_requests/1/diffs
Output of checks
GitLab.com, GitLab Enterprise Edition 11.9.0-rc8-ee
Based on timing from customer report (2019-03-15), this may have been introduced in
rc7, thus marking as regression (please remove if that's not the case)