New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebasing MR gets stuck in a loop and uses up all CI minutes #6690
Comments
We had the same issue, and can provide logs if you need some more |
If you look in the dashboard, how many Renovate "jobs" were run during this time? I'm interested in whether each rebase somehow trigger another Renovate job? Otherwise it should have run ~hourly if there wasn't any webhook events triggering further runs. |
@rarkins Maybe we have again an issue with not updating pr description after pushing new commit? |
@viceice yes, I suspect that too. Curious why so many pipelines triggered though. |
🎉 This issue has been resolved in version 21.24.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
What Renovate type are you using?
GitLab hosted app
Describe the bug
If you tick the box on a merge request called "If you want to rebase/retry this MR, check this box", Rennovate gets stuck in a loop constantly rebasing and pushing new commits to the branch. This uses up our month's worth of 2000 CI minutes in under half an hour.
Relevant debug logs
Rennovate config:
Logs from one of the 100 jobs that started before we could cancel them: https://gist.github.com/k-yle/9326a01eead03b68da3f676bed7381ef
To Reproduce
Additional context
Maybe something to do with
stabilityDays
, it's quite buggy on GitLab when you combine it with"prCreation": "not-pending"
Not sure if this is relevant but I saw this in the logs, it looks odd, not sure why it says
reuseExistingBranch: false
because it does re-use the same branch.The text was updated successfully, but these errors were encountered: