Open marslo opened 7 years ago
From the http://<JENKINS_URL>/log/gitlab-jenkins.log
, looks it's stuck at the LDAP certification? USER001.MY.COMPANY.COM:8080
is the our LDAP server. But, normally, we are using the LDAP server without port 8080
.
This looks mostly like a GitLab issue - it is returning a 504 for our requests. I don't really know why that would be. I would check the GitLab server logs and see if there is any more information there.
We should probably handle this case more gracefully though.
Thanks @omehegan, if you need any logs or something, I can help.
@omehegan I've got the same problem and no influence on the used GitLab version. Do you have any suggestions for a workaround?
Hi @omehegan, I've upgraded the Gitlab to the latest version 9.0.0
. However, this issue still exists.
I've check the Gitlab, and found something, maybe related with this issue. The Jenkins CI cannot be found in Project -> Settings -> Integrations -> Project services. And, it's actually introduced in gitlab official website
Here the screenshot:
@Restage, right now, I'm using the webhook function in Gitlab Project Settings. And setup Authentication Token
in Jenkins Trigger builds remotely
. It's kind of annoying, you have to setup webhook for each Project independently. And if there's something changed, you have to setup webhook URL again (e.g. with parameter or not).
Here screenshot in Gitlab -> Project -> Settings -> Integrations:
I don't think this is necessarily a bug in GitLab or in the plugin. It looks like a GitLab configuration issue. I would try using sudo gitlab-ctl tail
to observe the GitLab logs when it is returning a 403 to Jenkins. That may shed some light on why it is doing that.
Hi @omehegan, is there any workaround to fix it? Thanks.
Hi @omehengan,
Well.... I 'fixed' this issue. Maybe it's not a issue actually.
Here is my situation:
Due to the company network environment, the Jenkins has been setup the proxy in Manage Jenkins -> Manage Plugins -> Advanced -> HTTP Proxy Configuration (http://
Here is what I did:
I've added the Gitlab url in the No Proxy Host
input box, and it works now....
Here the comparison:
Before setup the No Proxy Host
After setup the No Proxy Host
OK. So mostly an environment issue. On the plugin side, we should improve the behavior so we don't throw an exception when we get this error back (from the proxy server, in this case).
Yes. I didn't also realized it was caused of proxy settings in plugin management.
Maybe chose the exactly option in checkbox named "API-LEVEL" can help :smile: . @omehegan
Issue
Context
1.1.x
Logs & Traces
Please include any relevant log that could serve to better understand the source of your issue For Jenkins Gitlab Plugin logs, follow instruction in User Support section. For Gitlab logs, ask an administrator to provide you the relevant Gitlab logs.
What I did:
Go to Jenkins Manage Jenkins -> Configure System -> Gitlab, click Test Connection.
The
http://<JENKINS_URL>/log/gitlab-jenkins.log
shows:The
Configure System (http://<JENKINS_URL>/configure)
shows:The
/var/log/jenkins/jenkins.log
shows:The Gitlab API token should be right. Cause Gitlab API URL can be visit succeed by using
provivate_token
:Problem description
Describe your problem in a meaningful way: