feat(gitlab): increase merge request status check timeout to 300 sec #25953
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Increase retry times to 35 when requesting merge request status from gitlab when platform automerge is enabled.
Context
In some self-hosted Gitlab installation with self-hosted Gitlab Runners and a lot of workload most of the times pipelines need more than the very short timeout set before (7.5 sec) to be created when creating a MR. This results in 405 Method not allowed failure responses when trying to set a merge request to auto-merge. Increasing the timeout to a large enough number solves this issue. See discussion in this issue:
Closes #25946
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: