-
Notifications
You must be signed in to change notification settings - Fork 614
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
NullPointerException shows in gitlab-plugin 1.4.5 (fresh install) #521
Comments
From the |
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 |
@Restage, right now, I'm using the webhook function in Gitlab Project Settings. And setup |
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 |
Hi @omehegan, is there any workaround to fix it? |
Hi @omehengan, Well.... I 'fixed' this issue. Maybe it's not a issue actually. Here is my situation: Here is what I did: Here the comparison: |
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 😄 . @omehegan |
[readme] optimize fetching by only fetch the needed PR
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:
The configuration.
Jenkins can connect to Gitlab successfully
The error shows up.
The text was updated successfully, but these errors were encountered: