Hi Stephen,

Can you explain some more about what you mean by "relevant credentials for that 
URL" - and how you may determine what is relevant?

Currently for svn+ssh we don't need to add every single repositrory URL into 
Jenkins: I have defined one and one credential for Jenkins for 
svn+ssh://mysvnserver.foo.com/  even though the repositories are actually 
svn+ssh://mysvnserver.foo.com/svn/repo1, 
svn+ssh://mysvnserver.foo.com/svn/repo2 etc..

The other thing if you are doing this from a generic usability point is perhaps 
think about if multiple options are available being able to set one as a 
default such that users who are unsure of which option to choose will, if they 
do nothing, get the correct option 80% of the time.

/James


From: [email protected] 
[mailto:[email protected]] On Behalf Of Stephen Connolly
Sent: 08 August 2013 13:02
To: [email protected]
Subject: [POLL] how addicted are you to the current Subversion plugin's 
authentication model?

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]<mailto:[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.

Reply via email to