Well if the parameters are credentials, e.g. using the https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Binding+Plugin and the user has tied the credentials to their own user account scope, then the only credentials available to the build will be the global credentials and those of the user triggering the build.
So in that scenario, Joe can put his credentials into his user record and they will show in the drop down when Joe decides to trigger a build... but when Fred tried to re-trigger the build or even if Fred tries CLI submission using Joe's credential's UUID explicitly he still will not be able to inject Joes credentials as they are user scoped. Note: I have not verified that Jesse implemented lookup of user credentials in the credentials binding plugin, but the design of the credentials API is to allow this model. The final advantage is that if Joe changes his password and then triggers a rebuild, it will use his new password and not the old one! On 1 July 2014 15:30, Rob Mandeville <rmandevi...@dekaresearch.com> wrote: > I’m trying to implement a job that requires each user to enter their own > credentials. There is a password parameter, which is all well and good. > But if I remember correctly, the Rebuild Plugin allows you to rerun builds > with password parameters. This means that Jenkins remembers the password > you entered in such a way that it can retrieve it later (that is, even if > it’s stored encrypted, it can decrypt it). More practically, it means that > if Joe runs a build, I can later run a build as Joe by rebuilding his > build, changing everything but Joe’s username and password. > > > > Is there a way to get Jenkins to completely forget the password you > entered after it runs the job? > > > > --Rob > > > > ------------------------------ > This e-mail and the information, including any attachments it contains, > are intended to be a confidential communication only to the person or > entity to whom it is addressed and may contain information that is > privileged. If the reader of this message is not the intended recipient, > you are hereby notified that any dissemination, distribution or copying of > this communication is strictly prohibited. If you have received this > communication in error, please immediately notify the sender and destroy > the original message. > > Thank you. > > Please consider the environment before printing this email. > > -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- 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. For more options, visit https://groups.google.com/d/optout.
