On Tue, Aug 12, 2014 at 12:25 PM, Rui Travassos <[email protected]> wrote: > after some search I had found the SVN > Publisher https://wiki.jenkins-ci.org/display/JENKINS/SVN+Publisher. However > I could not configure it to work properly and […it seems] > the plugin is abandoned and has security problems like > store plain passwords. > > Then, I decided to write my own plugin to full fill my needs, et voilá, SVN > Deployer
Generally we want to avoid plugin sprawl; it confuses users. Is it feasible to just make the required changes to the existing plugin, using standard tricks like readResolve to migrate existing settings? (For example, a String user + String password can be converted to a String credentialsId by using CredentialsProvider to create a new StandardUsernamePasswordCredentials.) If not, and assuming the old plugin is truly abandoned, I would suggest naming the new plugin clearly as a successor to the original, and indicating this in the old one’s wiki page so the 1626 users of the old one (at last count) can see what they should switch to. -- 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/d/optout.
