Self hosted gitlab renovate runner automerge gives Response code 405 (Method Not Allowed) #31542
Replies: 1 comment
-
Just experienced the same problem. I had an issue where the The 405 race condition can maybe be explained by this: https://gitlab.com/gitlab-org/gitlab-foss/-/issues/26927#note_493901884 Would actually been nice if you could in fact configure Renovate the re-trigger a pipeline in a merge request if it has failed in the past. Our concrete example is that from time to time we are resource constrained and it would success on a second run. |
Beta Was this translation helpful? Give feedback.
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitLab
Please tell us more about your question or problem
I have deployed renovate-runner on my self hosted gitlab instance. Everything works fine, except when I try the automerge functionality I keep getting Response code 405 (Method Not Allowed). I am using the following config file on my repo:
Renovate correctly creates MR requests but when trying to automerge them it gets 405 code. Renovate bot is running as a Maintainer user which has all permissions to do merge requests. Also no other branch protections are enforced in the repo. I confirmed this testing the same API call renovate performs with postman (copying headers and using the same TOKEN as renovate is using), and I get 200 response code.
Any ideas how to investigate this or what could be the issue here? Below I posted also debug logs from my instance.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions