-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins ver. 2.164.3
job-dsl 1.74
ssh-credentials 1.16
-
-
job-dsl-plugin 1.79
Version 1.16 of the SSH Credentials plugin changed the plain SSH private key from String to a hudson.util.Secret.
This leads to the situation that Job DSL cannot be used to configure SSH credentials any longer.
This snippet works when using SSH Credentials plugin 1.15:
folder('foo') { properties { folderCredentialsProperty { domainCredentials { domainCredentials { domain { name(null) description(null) } credentials { basicSSHUserPrivateKey { scope('GLOBAL') id('my-ssh') description('My SSH Credentials') username('me') passphrase('') privateKeySource { directEntryPrivateKeySource { privateKey('SSH-PRIVATE-KEY-HERE') } } } } } } } } }
But with SSH Credentials version 1.16, the privateKeySource directive shows as empty in the Job DSL's API browser.
Maybe there's a way to also support hudson.util.Secret in Job DSL (by simply wrapping Strings into Secret.fromString(...))?
- is blocked by
-
JENKINS-34173 DescribableModel rejects PasswordParameterValue due to use of Secret
- Open
- is related to
-
JENKINS-62337 "password" parameter no longer available
- Open
-
JENKINS-59971 Unable to create folder credentials for plain-credentials-plugin
- In Review
-
JENKINS-44681 JobDSL Folder Creation Destroys Credentials
- Closed
- relates to
-
JENKINS-54345 Job-DSL RTC Build Definition
- Open
- links to