Usually the adminstrator of a Jenkins is reponsible to register credentials
with a useful (readable) name. If those admin forget to give a name Jenkins
does it for your which results usually in something like this:
"b86bc2b6-994b-4811-ac98-0f35e9a9b114'
Of course you don't wanna have such ID's in your coded pipeline. Consider
you might have running your pipeline on different Jenkins providing the same
credentials (names) your project should be able to build without code
changes.
It might be a permission thing that you cannot see the credentials.
On Wednesday, April 19, 2017 at 1:19:15 PM UTC+2, David Aldrich wrote:
>
> Hi
>
> I have created a simple pipeline job that is intended just to check out a
> working copy from svn initially.
>
> Here's the script:
>
> node {
> echo 'Hello World'
>
> stage('Checkout') {
> checkout([$class: 'SubversionSCM',
> additionalCredentials: [],
> excludedCommitMessages: '',
> excludedRegions: '',
> excludedRevprop: '',
> excludedUsers: 'buildbot',
> filterChangelog: false,
> ignoreDirPropChanges: false,
> includedRegions: '',
> locations: [[credentialsId:
> 'b86bc2b6-994b-4811-ac98-0f35e9a9b114',
> depthOption: 'infinity',
> ignoreExternalsOption: true,
> local: '.',
> remote: "<snip>"]],
> workspaceUpdater: [$class: 'UpdateUpdater']])
> }
> }
>
> Is the script valid?
>
> How do I determine the 'credentialsId' ? (I have credentials set up in
> non-pipeline jobs already).
>
> Best regards
>
> David
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/f668c4f1-e127-4008-a368-12e3ae10d1f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
