This is more or less the current implementation, but as git-plugin does a git fecth for remote logical name "origin" plugin has to set remote.<origin>.url. Maybe just un-setting would avoid keeping this secret data in workspace
anyway, please remember current "solution" is to have the password in plain text in job configuration :P 2013/10/9 Jesse Glick <[email protected]> > On Wed, Oct 9, 2013 at 8:49 AM, nicolas de loof > <[email protected]> wrote: > > Just like svn does with ~/.subversion, and probably other tools. > > FWIW the Mercurial plugin in 1.48 just uses --config (a global option) > to send a (masked) username and password to hg commands. Is there no > equivalent for Git? If nothing else, you should be able to inject > user:pass@ into the remote URL and then pass this (masked) in the > arguments list for commands taking an optional remote name/URL. > > Storing the password inside the workspace seems like a very bad > idea—means anyone with workspace browse permission can grab it, and it > could inadvertently wind up in artifacts. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
