On Monday, August 31, 2015 at 1:25:41 PM UTC-7, Guenther, Marc(AWF) wrote: > > On Monday, August 31, 2015 at 10:50:59 AM UTC-7, milki milk wrote: > > Another thing that plagues my use of JJB is the fact that Security > credentials, like those uses in the git scm configuration, must be > hardcoded the Credential ID string. This string is unique to each Jenkins > master instance though which means jobs with these strings must be uniquely > defined per instance. Do you use Credentials in your JJB definition files? > If so, how do you manage the hardcoded strings? > > Recent version 1.21 of Credentials Plugin allows to specify meaningful IDs > for your credentials, so you can reuse them over several Jenkins masters, > which is veeeeery convenient. You could also use EnvInject-Plugin to inject > credentials as build variables, but Credentials Plugin is more secure. >
! This is awesome. meaningful ids is exactly solves my issue. Nice find. -milki -- 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/241a8ffa-7b1f-4eb0-849d-9f26befba207%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
