My understanding is that the ref attribute in Gitlab’s status API has a misleading name. In a MR context Drone seems to post the build status with a refs/merge-requests/*/head like ref, where Gitlab expects to find the name of the upstream branch instead.
Am I right ? And, who do you feel I should bug with this issue ?
DRONE_HOST is prorperly set in my docker-compose file (DRONE_HOST=https://drone.companyname.tld).
I’ve used the Gitlab’s Ruby CLI to fetch the pipelines objects as the reporter of the Gitlab issue did . I’ve reviewed only a small subset, but the pipeline I found showing a status icon in the MR view was the one having a “ref: branch” like attribute. The other pipelines (“ref: refs/merge-requests/*/head” like) don’t show.
Hey . Were you able to resolve this? I followed https://docs.drone.io/intro/gitlab/single-machine/ and builds are being picked up just fine by drone, but, unfortunately, no status is displayed on gitlab side :-/ . Is there anything else I should do to make gitlab acknowledge drone?
This is not something I am able to investigate or work on at the moment due to conflicting priorities, so if someone wants to accelerate a solution I recommend testing and sending a patch to https://github.com/drone/go-scm. Otherwise, I should be able to take a look at this in ~6 weeks.