Commits API
Summary
"Post the build status to a commit" fails with 404, even if user has all required permissions and commit is available (tested using web ui and on "get single commit" function, too)
Steps to reproduce
- Create a fork of an existing repository,
- Create a branch in forked repository,
- Create/Push a commit containing a real change to any of the contents,
- Create a merge request to the original repository,
- Try to set commit status to the original repository using v3 api (on the commit referencing the merge request),
- Get http response 404
⚡ ⚡ ⚡
Example Project
Ok, did so in
https://gitlab.com/tr1gg3rh4ppy/original-repository (original repo) https://gitlab.com/robs-pg/original-repository (forked repo)
described MR is here:
https://gitlab.com/tr1gg3rh4ppy/original-repository/merge_requests/1
What is the current bug behavior?
Did the above and the following (read) works fine (using GET request, see docs):
while (doing a POST request, see docs)
does
Since we use this in our local CI instance (JetBrains Teamcity 10.x), I used the v3 api, but the same behaviour occurs in v4 api, too.
What is the expected correct behavior?
The state should be correctly updated, as documented.
Relevant logs and/or screenshots
.
Output of checks
The above happens on gitlab.com, and on our "on-premise" installation.
Results of GitLab environment info
.
Results of GitLab application Check
.
Possible fixes
.