[JIRA] (JENKINS-50754) "ERROR: Could not find credentials matching (rolename)" when using AWS role

2018-11-07 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50754  
 
 
  "ERROR: Could not find credentials matching (rolename)" when using AWS role   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 docker-commons-plugin  
 
 
Component/s: 
 pipeline-model-definition-plugin  
 
 
Assignee: 
 Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50754) "ERROR: Could not find credentials matching (rolename)" when using AWS role

2018-05-18 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Andrew Bayer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong component.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50754  
 
 
  "ERROR: Could not find credentials matching (rolename)" when using AWS role   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 pipeline-model-definition-plugin  
 
 
Component/s: 
 docker-commons-plugin  
 
 
Assignee: 
 Jesse Glick Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-

[JIRA] (JENKINS-50754) "ERROR: Could not find credentials matching (rolename)" when using AWS role

2018-04-11 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-50754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "ERROR: Could not find credentials matching (rolename)" when using AWS role   
 

  
 
 
 
 

 
 Just to clarify, does this ID represent the "AWS Credentials" type? If yes, the plugin won't be able to use them. Only "Docker Registry Token" credentials type is supported by the plugin according to the code, all other credentials will be ignored. https://github.com/jenkinsci/docker-commons-plugin/blob/e00c616a847630fccf637e891000813a7b441ceb/src/main/java/org/jenkinsci/plugins/docker/commons/credentials/DockerRegistryEndpoint.java#L184-L186 The error message could be improved for sure. It could indicate the required type/domain at least  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50754) "ERROR: Could not find credentials matching (rolename)" when using AWS role

2018-04-11 Thread block....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon B created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50754  
 
 
  "ERROR: Could not find credentials matching (rolename)" when using AWS role   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 docker-commons-plugin  
 
 
Created: 
 2018-04-11 21:22  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jon B  
 

  
 
 
 
 

 
 My pipeline looks like this: 

 

pipeline {
 agent {
 docker { 
 image '.dkr.ecr.us-west-2.amazonaws.com//cicd-debian-worker:v0.0.2'
 label ''
 registryUrl 'https://.dkr.ecr.us-west-2.amazonaws.com/'
 registryCredentialsId 'JENKINS_SLAVE_AWS_ROLE'
 }
}
... 

 I have also set an AWS credential for which I set the ARN to the role ARN I'm interested in into the global namespace in the credentials store. When I run my pipeline, it fails with: 

 

ERROR: Could not find credentials matching JENKINS_SLAVE_AWS_ROLE 

 I'm 100% sure the credential exists with that name.