Failed pipeline status emails not sent for scheduled pipeline when GitLab CI configuration becomes invalid
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Failed pipeline status emails are not sent, when a project build is running on a schedule and the gitlab-ci.yml becomes invalid, for example due to breaking changes in GitLab.
It appears to be because the pipeline does not get created.
Steps to reproduce
- Have buildable project
- Setup a pipeline schedule
- Define integrations with
Pipeline status emailsand usingNotify only broken pipelines - Something external to the project causes the gitlab-ci.yml file to become invalid, fx by using a CI/CD template that breaks due to breaking changes in GitLab.
Example Project
What is the current bug behavior?
No pipeline status email is being sent, requiring incidental discovery that the pipeline was not running as per schedule.
What is the expected correct behavior?
A pipeline status email that directs attention that the pipeline cannot be created due to invalid gitlab-ci.yml
Relevant logs and/or screenshots
Could not determine any logs to indicate that the schedule failed to start.
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)