> > Hi, > to a certain extent it depends on how paranoid You allow yourself to get ;-)
One solution could be to use indirection, e.g. via the Config File Provider Plugin. Use an arbitrary token in your job description, and in an additional build step access a configuration file to read the actual access token that is necessary ... via simple properties. That way You could use different IDs for each Jenkins instance, if that is a requirement, and the mapping is done via the configuration file. Cheers, Steffen -- 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/cfc7463c-be61-46e3-9eeb-b170a22dd1ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
