Scheduled pipeline with branch deleted doesn't report error
Summary
When a scheduled pipeline is set against a branch which gets deleted, nothing notify the user of such wrong setup except that the pipeline gets scheduled by never get to actually run. Furthermore is still possible to trigger it manually and popup show correct scheduling even though the job never starts.
Steps to reproduce
- Set a scheduled pipeline against a branch
- Delete the branch or merge the branch in master from the merge request with the delete branch option
- Manually trigger such schedule
What is the current bug behavior?
- Blue pop appear saying 'pipeline was scheduled'
- The job never starts
- The scheduled pipeline stop triggering the job at the cron interval
What is the expected correct behavior?
- The schedule is marked with an error state mentioning the specific issue 'branch doesn't exist'
- Same in schedule edit mode
Relevant logs and/or screenshots
Edited by Jason Yavorska