-
Notifications
You must be signed in to change notification settings - Fork 611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge Request CI status not updating #56
Comments
Can you post any logs from Jenkins? |
Here are some of the logs I have from the jenkins.log. This is when one of my builds kicked off from a Merge Request and failed. The CI Status in Gitlab never gets updated at all. Let me know if there is anything else I can provide. Feb 11, 2015 9:58:50 AM com.dabsquared.gitlabjenkins.GitLabWebHook getDynamic |
I'm running into the same issue as well:
Returns nothing
Returns:
Logs from jenkins:
|
@ejhayes and @mildewonrice what version of Gitlab? |
I'm using GitLab 7.6.2 |
I am running 7.7.2-ee |
This seems like more of a plugin issue rather than a gitlab issue:
|
This same problem. GitLab 7.5.3, Jenkins 1.580.2 using Gitlab-plugin 1.1.15 |
I have the same problem on Gitlab 7.8.4, Jenkins 1.580.3 using Gitlab-plugin 1.1.15 status.json returns pending for completed builds, and build page is blank |
Upgrade to version 1.1.17 resolve issue for me. |
Still a problem for me on 1.1.17 |
1.1.17 fixed this problem for me on Gitlab 7.8.1-ee. |
@twk3 and @ndcampbell is this for a merge request between forks or between branches of the same repos? Its possible that one works while the other does not. |
And could be related to #61 |
For between branches of the same repo for me. But the repo itself is a fork. |
@twk3 can you post the logs while it is requesting the status. There was more logging added in the lastest release. |
Log level is set at INFO, all I get for a build status call is
For pushing to to a merge request branch I get:
|
Updated to latest plugin, and changed log level to fine. The get Status log didn't change. Doing a push to a merge results in:
(username and url changed) |
If you go to the url: /project/PROJECT_NAME/builds/COMMIT_SHA1/status.json with your project name in jenkins and "2a3c05cad9e3e1db66bc6dc8b4c3c6e5c893e847" from your log above what do you get |
On the jenkins box^ |
The log says
and the response is:
|
Ok and i would assume the merge request page shows a pending status? |
Yep, but build is finished, and successful |
Ok So this function in GitlabWebHook: is not returning a build from the commit sha1. |
I'm having the same issue as well. |
This issue is happening again for me on Gitlab 7.10 for branch merges. I am using the latest version of the plugin. CI status is stuck at pending. It was working for me just fine in Gitlab 7.8 |
@ndcampbell This is broken when using Gitlab 7.10 as Gitlab has changed the CI integration API. See #74 for details. |
@ndcampbell this should be fixed in the latest release. Can you confirm? |
@bassrock yeah, I can confirm. Looks to be working great in 7.10 with the latest release. |
good to hear |
I still have this issue on the latest plugin and gitlab 7.10. The older 1.1.3 plugin is still working I will try and debug at some point, and find why GitlabWebHook doesn't return a build in my case. |
Only the older version (1.1.3) of this plugin is working with the GitLab 7.2.1. To build from all branches (including new ones), I am using the polling method triggered by a Web Hook in GitLab, using a URL like this: http://JENKINS_URL/git/notifyCommit?url=URL_GIT_REPOSITORY With new new plugin version, the status page on Merge Request in GitLab is showing "pending", when I downgraded to 1.1.3, it started to show "passed". Just to reinforce, no other configuration was changed, only did the downgrade of the plugin. |
I have the same problem for gitlab 7.9.2, jenkins 1.596 and plugin 1.1.25 |
…ents Prepend newline for job comments if the message already contains comments
On a Gitlab merge request the CI status stays at "CI build pending for 6f3ca78b. Build page". The Build page link does not go to the build status (just goes to a blank Jenkins page) and even when the build is successful this pending message is never changed.
The text was updated successfully, but these errors were encountered: