Hi Nicolas, I opened https://issues.jenkins-ci.org/browse/JENKINS-19974 for an issue I could find testing 2.0-beta-3
Vincent 2013/10/10 Vincent Latombe <[email protected]> > Thanks nicolas, i'll give it a try asap > > Vincent > Le 10 oct. 2013 12:00, "nicolas de loof" <[email protected]> a > écrit : > > implemented, and released as 2.0-beta-3 >> >> I'd like to give it some time for live test, then will release 2.0 (final) >> >> >> 2013/10/9 nicolas de loof <[email protected]> >> >>> right, will experiment with this option. >>> >>> >>> 2013/10/9 Vincent Latombe <[email protected]> >>> >>>> Another alternative would be to fetch/push using anonymous remote (git >>>> fetch http://user:pwd@gitserver/myrepo <refspec>), that way it is >>>> never written in the repo config. >>>> >>>> Vincent >>>> >>>> >>>> 2013/10/9 nicolas de loof <[email protected]> >>>> >>>>> 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. >>>>> >>>> >>>> -- >>>> 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. >> > -- 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.
