-
Notifications
You must be signed in to change notification settings - Fork 74
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
Jenkins is failing due to external Id is required in the latest release for IAM role #116
Comments
I see a very similar issue with the EC2 Fleet plugin, I had opened this issue in Jenkins JIRA as https://issues.jenkins.io/browse/JENKINS-67452 |
AWS credentials plugin version 1.33 has a bug that causes builds to fail: jenkinsci/aws-credentials-plugin#116 Temporarily keep at existing version, but update other plugins
How can we get some attention on this issue? |
This didn't seem to work for me... I uploaded this version and restarted, and got a large traceback: 2022-02-04 19:44:21.312+0000 [id=30] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed ConfigurationAsCode.init |
the next build should be better. should be in https://ci.jenkins.io/job/Plugins/job/aws-credentials-plugin/job/PR-125/2/ under artifacts when the build completes |
This version (aws-credentials-1.34-rc182.5fcd8bb8776d.hpi) is definitely better, doesn't choke on the Jenkins restart. Seems at the moment to work as expected. Thanks for working on this! |
Version report
Jenkins and plugins versions report:
Reproduction steps
Results
Expected result:
Jenkins to grab the role and perform AWS tasks
Actual result:
com.amazonaws.services.securitytoken.model.AWSSecurityTokenServiceException: 1 validation error detected: Value '' at 'externalId' failed to satisfy constraint: Member must have length greater than or equal to 2 (Service: AWSSecurityTokenService
The text was updated successfully, but these errors were encountered: