> On 21.12.2015, at 23:49, Joe Ferr wrote:
>
> I'd use the Mask Password plugin to hide the exposed token from the console
> output so I don't think there would be a way to steal others users API tokens.
That plugin can only hide build parameters and previously defined strings. Do
you want to
Hi,
Jobddsl does support the credential plugin indeed.
https://github.com/jenkinsci/job-dsl-plugin/wiki/Handling-Credentials
Cheers
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails fr
I'd use the Mask Password plugin to hide the exposed token from the console
output so I don't think there would be a way to steal others users API
tokens.
A password parameter would work but it means that they need to login
twice...Not really a big deal; they've already logged into Jenkins. I
> On 21.12.2015, at 23:00, Joe Ferr 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'
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 g
