Thanks for the idea! In the meantime I also thought of a different idea:
1. having global properties for the auth token, e.g. Name: MY_TOKEN Value: 123 2. Access the token directly from the job dsl, e.g. authenticationToken(MY_TOKEN) Since the seed-job has access to the environment you from the job-dsl have access too. Best, Matthias On Friday, 25 August 2017 11:44:32 UTC+2, Steffen Elste wrote: > > 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/54223c4f-4a18-4474-97e2-c6fc62ad74c4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
