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. On 08.08.2013, at 14:02, Stephen Connolly <[email protected]> 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]. > 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]. For more options, visit https://groups.google.com/groups/opt_out.
