We use the gradle/groovy dsl to create our jenkins jobs. We have a need to have parameterized jenkins jobs which create job-sets+views to avoid various folks needing to run gradle scripts/pass parameters in order to create job sets. For example a job set might retrieve source from a specific git task branch then build a bunch of components which get uploaded to Nexus.
I can use a specific users username/api token in the gradle script, but it would be much cleaner if the current logged in user's api token was somehow exposed (as an env var?)/ made available to my gradle script. thanks, Joe -- 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/4aaa8acb-60d9-4924-ae51-7b0b5172ce03%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
