Skip to content
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

gitlab global settings "test connection" fails unconditionally #669

Closed
a2f0 opened this issue Nov 17, 2017 · 2 comments
Closed

gitlab global settings "test connection" fails unconditionally #669

a2f0 opened this issue Nov 17, 2017 · 2 comments

Comments

@a2f0
Copy link

a2f0 commented Nov 17, 2017

Issue

Context

  • Gitlab plugin version: 1.4.8 & 1.5.1
  • Gitlab version: https://gitlab.com
  • Jenkins version: 2.73.3 & 2.60.3
  • Job type: N/A

Logs & Traces

Nov 16, 2017 6:30:01 PM FINEST com.dabsquared.gitlabjenkins.gitlab.GitLabClientBuilder
Call GitLab:
HTTP method: HEAD
URL: https://gitlab.com/api/v3/user
Request headers: [
Accept = [application/json],
PRIVATE-TOKEN = [****FILTERED****]
]
Nov 16, 2017 6:30:02 PM FINEST com.dabsquared.gitlabjenkins.gitlab.GitLabClientBuilder
Got response from GitLab:
URL: https://gitlab.com/api/v3/user
Status: 400 Bad Request
Response headers: [
Cache-Control = [no-cache],
Connection = [keep-alive],
Content-Type = [text/html]
]
Response body: 

Problem description

This problem is easily reproducible. I have a feeling it is related Gitlab updating their platform today as my Gitlab connection was working fine but broke suddenly today. The issue can be reproduced by:

  1. Do a clean pull of the jenkins docker image
  2. Install the gitlab plugin upon first setup
  3. Configure an API key credential in https://gitlab.com
  4. In Jenkins global setting, configure the credential and https://gitlab.com and click "Test Connection". This will generate an ERROR. The com.dabsquared debug log generated by this failure is above. I get the same results with using the v4 api on the 1.5.1 plugin.
@omehegan
Copy link
Member

Maybe related to #608 ? Need @dblessing or someone from GitLab to take a look.

@a2f0
Copy link
Author

a2f0 commented Nov 17, 2017

Thank you for your support @omehegan & @dblessing. Whatever problem this is/was has appeared to go away on its own. I am resolving this issue.

@a2f0 a2f0 closed this as completed Nov 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants