-
Bug
-
Resolution: Fixed
-
Blocker
-
Gitlab Plugin 1.3.0. Jenkins 2.7.1 hosted on Windows 7 64-bit, Java 1.8 64-bit. Client is Chrome 51 on Windows 10
On Manage Jenkins -> Configure System, in the Gitlab section, there's a Credentials section that had a drop-down list where I should be able to specify an API Token. The drop down says "-none" and has no other options. If I choose Add -> Jenkins, then under Kind I can select "GitLab API token" and put in the info, and click Add. But the credential I've added does not show up in the drop-down, so I can't select it, and I have the red "API Token for Gitlab access required" message.
I expect to be able to see the API token credential I have added in the drop-down list so I can select it and connect. But it is not there.
As a result I am unable to use the plugin at all.
[JENKINS-36863] [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Tyrel Haveman
created issue -
| Workflow | Original: JNJira [ 173610 ] | New: JNJira + In-Review [ 185229 ] |
Alex Chapman
made changes -
| Attachment | New: support_2016-08-03_03.23.23.zip [ 33507 ] |
Alex Chapman
made changes -
| Attachment | New: jenkins-gitlab-api-token-bug.png [ 33508 ] |
Alex Chapman
added a comment - I'm having the same issue. Attaching support bundle and screenshot: support_2016-08-03_03.23.23.zip
Alex Chapman
added a comment - I'm having the same issue. Attaching support bundle and screenshot: support_2016-08-03_03.23.23.zip I'm hitting the same issue on Jenkins v1.651.2 with the Gitlab plugin v1.3.0. I did create a Credential of type "GitLab API token" prior to creating the connection.
Tobias W.
added a comment - Having the same issue on Jenkins 2.11 with version 1.3.0 of the Gitlab plugin. Credentials do not show up in the dropdown, no matter if they are created separately or on the fly during plugin configuration.
Tobias W.
added a comment - Having the same issue on Jenkins 2.11 with version 1.3.0 of the Gitlab plugin. Credentials do not show up in the dropdown, no matter if they are created separately or on the fly during plugin configuration. 
Mark Parker
added a comment - Having the same issue as well. Jenkins 2.7 and Gitlab 1.3.0 AND Jenkins 1.651.3 and Gitlab 1.3.0.
The token appears to get created, because when I try to create another token with the same name, it tells me "This ID already in use"
Mark Parker
added a comment - Having the same issue as well. Jenkins 2.7 and Gitlab 1.3.0 AND Jenkins 1.651.3 and Gitlab 1.3.0.
The token appears to get created, because when I try to create another token with the same name, it tells me "This ID already in use" 
Drew Blessing
added a comment - I can reproduce on a Mac, Jenkins version 1.651.2 brand new install, in Chrome, Firefox and Safari.
Drew Blessing
added a comment - I can reproduce on a Mac, Jenkins version 1.651.2 brand new install, in Chrome, Firefox and Safari. 
There was already an issue for this on GitHub but unfortunately I can't reproduce it. So may I ask you for installing the following plugin: Support Core Plugin in your Jenkins and generate a support bundle. This will generate a Dockerfile that can be used to generate a docker image that should contain a Jenkins with a similar setup to yours. Maybe this helps to identify the cause for this issue.