Details
-
Story
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Done
-
None
-
Pipeline Config 0.1
Description
What would be nice and idiomatic is to be able to something like:
environment { AWS_ACCESS_KEY_ID = credentials(id='amazonKeyId') AWS_ACESS_KEY_SECRET = credentials(id='passwordId') }
(or something more configgy looking). This can be limited to the single secret case if needed (ie not username/password).
Using various incarnations of the wrapper:
withCredentials([[$class: 'UsernamePasswordMultiBinding', credentialsId: '', passwordVariable: 'AWS_SECRET', usernameVariable: 'AWS_ID']]) { // some block }
You can, I think get credentials back out but it is seems less configgy for common scenarious.
Code changed in jenkins
User: Robert Sandell
Path:
pipeline-model-definition/pom.xml
pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/steps/CredentialWrapperStepTest.java
http://jenkins-ci.org/commit/pipeline-model-definition-plugin/bec0c4be0503c5703e9d6e0da24833bc999d1372
Log:
JENKINS-37778Fix test after mergeSomething unrelated in the shared libraries caused the tests to fail
bumping the dependency down one version to fix that.
An npe caused bu the credentials folder property to not be correctly initialized also fixed.