Open dominik42 opened 5 years ago
have you found a workaround?
No.
+1
I've had the same issue on my gitlab server as well. It turned out to be be a problem with my apache reverse proxy configuration. Adding nocanon
to ProxyPass
and adding AllowEncodedSlashes NoDecode
solved it.
The bug report https://gitlab.com/gitlab-org/gitlab-foss/issues/35079#note_76374269 was very helpful for fixing it on my side.
Hello! Is there any update on this?
I'm currently trying to set up a Multibranch pipeline project that will listen to a GitLab webhook for merge request events and will trigger a build for each branch but as you mentioned the updateGitlabCommitStatus
is not updating anything on GitLab. And I can see on the logs updateGitlabCommitStatus
being called with no errors but nothing updating on GitLab with the current pipeline
If I set a regular pipeline project it all works as expected. But there is the issue of only having one workspace per branch which is why I wanted to have a Multibranch project to have everything separated
EDIT:
.git
at the end solved my issue
Issue
For any multibranch pipeline job, the gitlab status isn't updated., but it works perfectly for normal pipeline jobs. The gitlab project name of this failed jobs contains group and subgroup names, separated by
/
(slash). This slash is then URL encoded by the gitlab plugin for building the request URL at gitlab site for retrieving project releated infos (ids, commits etc.) Those requests failed with404 Not found
. Already stumple upon #462 and #691 but I do not see that it should be an nginx@gitlab issue. I also configured the gitlab connection for the multi branch pipeline:I'm wondering that for other non-multibranch-jobs, the retrieving of the project ids from gitlab returns successfully and those ids are used for the URLs afterwards. For the failing multibranch jobs, this retrieving failed and then this encoded project name
Context
Logs & Traces