> On 21.12.2015, at 23:00, Joe Ferr <jf...@iqnavigator.com> wrote: > > much cleaner if the current logged in user's api token was somehow exposed > (as an env var?)/ made available to my gradle script.
And by "cleaner" you mean "enable your users to steal other users' API tokens just because they clicked 'Build Now' on some job"? This looks like a job for a password parameter (because that's what it is), or maybe Credentials. Alternatively, you can probably achieve this with some (Groovy) scripting, e.g. System groovy build steps from the Groovy plugin. Some familiarity with Jenkins internals is required. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4C58587F-3C39-4366-B2EF-9961C9619FA4%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
