On Thursday, 8 August 2013, Daniel Beck wrote: > This would be really awesome. Right now, credentials handling in > Subversion plugin is rather intransparent. Reusing known credentials > (unless they're a repo's default) isn't easy either. > > HOWEVER this needs a better upgrade path than SSH credentials. I can deal > with a dozen duplicates of the same three SSH credentials, but creating one > credential per Subversion job (or remote URL) would be absolute madness.
Well hopefully I can create better matching rules... Eg consolidate better than happened in ssh slaves initially... Given the grab-bag nature of svn auth as it exists right now, we certainly should be able to produce a minimum set. If you can share example test cases in upgrading to ssh slaves where you got duplicates I can try to improve that logic (I am suspecting the parallel loading in Jenkins may be to blame for some of your issues) (You know how to reach me off list if you have stuff you can't share public... And this is part of a work-sponsored effort... If slightly tangential and only the first visible tips of the stuff we have coming down the road) > On 08.08.2013, at 14:02, Stephen Connolly > <[email protected]<javascript:;>> > wrote: > > > In working on integrating with the Credentials plugin there is, from my > point of view, a lot of insanity and crazy ways of doing auth. > > > > How attached are people to the existing way? > > > > The way I want to deliver is that you have a drop down underneath any of > the module remote url fields which lists the relevant credentials for that > URL (including none) and you would always make a selection (even if that > selection is leaving the default of "none" selected) > > > > I would like to ditch entirely the existing model of credentials and go > straight for this simplified model. > > > > What do people think? > > > > > > > > -- > > Sent from my phone > > > > -- > > 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] <javascript:;>. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > 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] <javascript:;>. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Sent from my phone -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
