Gitlab platformAutomerge is not working when pipeline creation takes more than 7.5 sec. #25946
Unanswered
fullstackcreatives
asked this question in
Request Help
Replies: 1 comment 6 replies
-
Which server/service is setting the pipeline and why does it take more than 7.5s? e.g. is this an internal gitlab thing or some external CI like Jenkins? |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us what version of Renovate you run.
latest
If you're self-hosting Renovate, select which platform you are using.
GitLab self-hosted
Was this something which used to work for you, and then stopped?
None
Describe the problem
Platform Automerge in Gitlab will set auto-merge in Gitlab when Merge Request option is set to "pipelines must succeed". Automerge can only be activated when the merge request has a pipeline associated to it. In some Gitlab installations the creation of a pipeline can take some time.
Renovate tries to set auto-merge here https://github.com/renovatebot/renovate/blob/main/lib/modules/platform/gitlab/index.ts#L650 latest after 7.5 sec timeout which on our platform is most of the times not enough time to create a pipeline. There for platform automerge is not set in the merge requests.
Relevant debug logs
Logs
Have you created a minimal reproduction repository?
Placeholder value, please select the correct response from the dropdown
Beta Was this translation helpful? Give feedback.
All reactions