Click on the link an a table is shown and there is the columns ID ... One note: if you forgot to provide a readable name you cannot change it. You have to re-create it then.
On Thursday, April 20, 2017 at 1:07:53 PM UTC+2, [email protected] wrote: > > When you click top/left on "Jenkins" (navigate to the mainpage) the link > to the credentials > should appear on the left side (short before build queue). > > On Thursday, April 20, 2017 at 12:59:31 PM UTC+2, David Aldrich wrote: >> >> Thanks for your reply. I am an admin so I should be able to see >> everything. Where should I look for the credentials? >> >> >> >> All our conventional jobs use the following credential seen on the job >> configuration page: >> >> >> >> >> >> Where should I look for the corresponding credentialId? >> >> >> >> Best regards >> >> >> >> David >> >> >> >> *From:* [email protected] [mailto:[email protected]] >> *Sent:* 20 April 2017 11:39 >> *To:* Jenkins Users <[email protected]> >> *Cc:* David Aldrich <[email protected]> >> *Subject:* Re: How to specify svn credentialsId in pipeline job? >> >> >> >> 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 >> >> >> >> Click here >> <https://www.mailcontrol.com/sr/PS9zzq4a5Y!GX2PQPOmvUs3oG7lEfVxCzPPmYDypv14txLmT1cqnLRGjWI!kNRHHlpLFCZWcu8GsCq9I+zBdpQ==> >> >> to report this email as spam. >> > -- 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/05550dc0-0343-46cd-8666-bb0fb19828b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
