[JIRA] (JENKINS-36877) Can't select credentials

8 views
Skip to first unread message

max.allan+jenkins@surevine.com (JIRA)

unread,
Jul 22, 2016, 9:12:04 AM7/22/16
to jenkinsc...@googlegroups.com
max allan created an issue
 
Jenkins / Bug JENKINS-36877
Can't select credentials
Issue Type: Bug Bug
Assignee: Francis Upton
Components: ec2-plugin
Created: 2016/Jul/22 1:11 PM
Environment: 1.35 of plugin Jenkins 2.14
Priority: Blocker Blocker
Reporter: max allan

Firstly the overview page for the plugin is out of date. It looks like the latest version has partially implemented the credentials management in Jenkins, you don't define the credentials in the plugin.
Then I can press the "Add" button, but after installing the plugin, only the "ssh" credential type was available. The plugin should probably add the "AWS key credentials" type.
But, I go off, enable the "Jenkins provider, AWS key credentials" and come back to the AWS plugin, I can now add an AWS access key/secret. Test/Save.
BUT the drop down in the Add Cloud still doesn't let me chose the credentials I entered.

I have tried the old method of setting them as environment variables in the jenkins user's .profile and restarting the plugin from the command line. Still no joy.

Finally, in the Configure System, Add new cloud section, the credentials' descriptive text says "Amazon EC2 Crendentials" (spurious "n")

So, I'm unable to choose the credentials set I defined and cannot use the plugin at all.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

max.allan+jenkins@surevine.com (JIRA)

unread,
Jul 22, 2016, 9:15:01 AM7/22/16
to jenkinsc...@googlegroups.com
max allan updated an issue
Change By: max allan
Firstly the overview usage page for the plugin is out of date. (https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin)
It looks like the latest version has partially implemented the credentials management in Jenkins, you don't define the credentials directly in the plugin any more .
Then I can press the "Add" button while adding an AWS cloud , but after installing the plugin, only the "ssh" credential type was available. The plugin should probably add the "AWS key credentials" type.

But, I go off, enable the "Jenkins provider, AWS key credentials" and come back to the AWS plugin, I can now add an AWS access key/secret. Test/Save.

Seems good.
BUT the drop down in the Add Cloud still doesn't let me chose the credentials I entered.

I have tried the old method of setting them as environment variables in the jenkins user's .profile and restarting the plugin from the command line. Still no joy.


Finally, in the Configure System, Add new cloud section, the credentials' descriptive text says "Amazon EC2 Crendentials" (spurious "n")


So, I'm unable to choose the credentials set I defined and cannot use the plugin at all.

jens@persson.cx (JIRA)

unread,
Nov 25, 2016, 8:48:56 AM11/25/16
to jenkinsc...@googlegroups.com
jens persson commented on Bug JENKINS-36877
 
Re: Can't select credentials

I'm having the same issue om a new jenkins instance using the following versions:

Jenkins: Version 2.19.3 docker instance
Docker: Version 1.11.2

Plugins:
Amazon EC2 plugin: Version 1.36
Amazon Web Services SDK: Version 1.11.37
Ant Plugin: Version 1.4
bouncycastle API Plugin: Version 2.16.0
Branch API Plugin: Version 1.11.1
build timeout plugin: Version 1.18
CloudBees Amazon Web Services Credentials Plugin: Version 1.16
Credentials Binding Plugin: Version 1.10
Credentials Plugin: Version 2.1.10
Display URL API: Version 0.5
Durable Task Plugin: Version 1.12
Email Extension Plugin: Version 2.52
External Monitor Job Type Plugin: Version 1.6
Folders Plugin: Version 5.13
Git client plugin: Version 2.1.0
Git plugin: Version 3.0.1
GIT server Plugin: Version 1.7
GitHub API Plugin: Version 1.80
GitHub Branch Source Plugin: Version 1.10
GitHub Organization Folder Plugin: Version 1.5
GitHub plugin: Version 1.23.1
Gradle Plugin: Version 1.25
Icon Shim Plugin: Version 2.0.3
Jackson 2 API Plugin: Version 2.7.3
JavaScript GUI Lib: ACE Editor bundle plugin: Version 1.1
JavaScript GUI Lib: Handlebars bundle plugin: Version 1.1.1
JavaScript GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin: Version 1.2.1
JavaScript GUI Lib: Moment.js bundle plugin: Version 1.1.1
JUnit Plugin: Version 1.19
LDAP Plugin: Version 1.13
Mailer Plugin: Version 1.18
MapDB API Plugin: Version 1.0.9.0
Matrix Authorization Strategy Plugin: Version 1.4
Matrix Project Plugin: Version 1.7.1
Node Iterator API Plugin: Version 1.5.0
OWASP Markup Formatter Plugin: Version 1.5
PAM Authentication plugin: Version 1.3
Pipeline: Version 2.4
Pipeline Graph Analysis Plugin: Version 1.2
Pipeline: API: Version 2.6
Pipeline: Basic Steps: Version 2.3
Pipeline: Build Step: Version 2.4
Pipeline: Groovy: Version 2.23
Pipeline: Input Step: Version 2.5
Pipeline: Job: Version 2.9
Pipeline: Milestone Step: Version 1.2
Pipeline: Multibranch: Version 2.9.2
Pipeline: Nodes and Processes: Version 2.5
Pipeline: REST API Plugin: Version 2.3
Pipeline: SCM Step: Version 2.3
Pipeline: Shared Groovy Libraries: Version 2.5
Pipeline: Stage Step: Version 2.2
Pipeline: Stage View Plugin: Version 2.3
Pipeline: Step API: Version 2.5
Pipeline: Supporting APIs: Version 2.11
Plain Credentials Plugin: Version 1.3
REPO plugin: Version 1.10.3
Resource Disposer Plugin: Version 0.3
SCM API Plugin: Version 1.3
Script Security Plugin: Version 1.24
SSH Credentials Plugin: Version 1.12
SSH Slaves plugin: Version 1.11
Structs Plugin: Version 1.5
Subversion Plug-in: Version 2.7.1
Timestamper: Version 1.8.7
Token Macro Plugin: Version 2.0
Windows Slaves Plugin: Version 1.2
Workspace Cleanup Plugin: Version 0.32

max.allan+jenkins@surevine.com (JIRA)

unread,
Nov 25, 2016, 9:46:05 AM11/25/16
to jenkinsc...@googlegroups.com

I'm not quite sure when, but at some point, the problem went away...
I have 2 sets of credentials now, only one appears in the plugin. Try adding more credentials and see if they appear!! Maybe there is an off by one error somewhere.

raihaan.shouhell@autodesk.com (JIRA)

unread,
Jun 28, 2019, 2:12:03 PM6/28/19
to jenkinsc...@googlegroups.com
Raihaan Shouhell resolved as Cannot Reproduce
Change By: Raihaan Shouhell
Status: Open Resolved
Resolution: Cannot Reproduce
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

369@holbertonschool.com (JIRA)

unread,
Jul 5, 2019, 5:25:02 PM7/5/19
to jenkinsc...@googlegroups.com
Bryan Leung updated an issue
Change By: Bryan Leung
Attachment: Screen Shot 2019-07-05 at 2.15.49 PM.png

369@holbertonschool.com (JIRA)

unread,
Jul 5, 2019, 5:25:04 PM7/5/19
to jenkinsc...@googlegroups.com

I have this problem. I enter my access and secret keys. I test the connection and it's fine. But then can't find that credential in the drop down menu but if I go into global credentials, I do find that it was added.

Also update the wiki guide please! It's very helpful for me to follow good documentation!

369@holbertonschool.com (JIRA)

unread,
Jul 5, 2019, 5:29:02 PM7/5/19
to jenkinsc...@googlegroups.com
Bryan Leung edited a comment on Bug JENKINS-36877
I have this problem. I enter also see that my access and secret keys. key that I test connected to Jenkins but can't see in the connection and AWS IAM dashboard was recently used. So it's fine. But then connected, just can't find that credential see it in the drop down menu but if I go into global credentials, I do find that it was added dropdown .

!Screen Shot 2019-07-05 at 2.15.49 PM.png|width=458,height=167!



Also update the wiki guide please! It's very helpful for me to follow good documentation!

369@holbertonschool.com (JIRA)

unread,
Jul 5, 2019, 5:32:02 PM7/5/19
to jenkinsc...@googlegroups.com
Bryan Leung edited a comment on Bug JENKINS-36877
I have this problem too where I created the account but I can't see it in the drop down menu. I went to global credentials and can verify that it was created. Testing shows it's connected. I just can't find it in the dropdown.å

!Screen Shot 2019-07-05 at 2.15.49 PM.png|width=407,height=148!

Also please update the docs, I find them very helpful when I follow along.

I
also see that my key that I connected to Jenkins but can't see in the AWS IAM dashboard was recently used. So it's connected, just can't see it in the dropdown.
Reply all
Reply to author
Forward
0 new messages