gitlab not triggering ci builds after some number of failures on given branch
Summary
CI/CD pipeline strange behaviour
Steps to reproduce
we can have a pipeline setup on a branch and make multiple commits for which the pipeline fail continuously
Example Project
NA
What is the current bug behavior?
I've setup some tests using CI/CD on a branch which used to trigger as soon as a new commit is there on this branch. My recent observation is it stopped triggering these pipelines for new commits after some failures recently. I manually run pipeline once and after that it started triggering pipelines for new commits and again stopped after some number of failures. I don't know if this is expected behaviour? If yes, how can I avoid this. If not what is the reason for not triggering pipelines for new commits?
What is the expected correct behavior?
It should trigger irrespective of whether the pipeline continuously fail or not
Relevant logs and/or screenshots
NA
Output of checks
NA
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)
Possible fixes
NA