SVN Deployer plugin

[Rui Travassos]

Hi,

I was looking for a plugin for jenkins to deploy some artifacts on a SVN repository after the job is done! So, 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 after some reading in comments and discussion groups 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 

Since I wrote this to my immediate needs, this is a beta version. I'll update git page with more info and instructions and do some more devs!

With my plugin you can add a post-build step and define one SVN repository. It uses the credentials interface of jenkins to setup the login in the. You can add several files(artifacts) to commit to the repository and define the destination path in the repository. To select the files you can use the file name or a file pattern (java regex) and commit multiple files. If the paths doesn't exists they are created.

Can you please create a jenkins repository with the name svn-deployer or other name you found more suitable. My username is travassos.
I used bitbucket (username: ruitravassos) but I also have a github account (username: sosimple)

Thanks

[Jesse Glick]

On Tue, Aug 12, 2014 at 12:25 PM, Rui Travassos <rui.tr...@gmail.com> 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.

[Rui Travassos]

Hi!

For me it's ok using the old plugin name but, in a quick analysis, the plugins won't be full compatible. It has very old dependencies, fields that does not makes sense since mine supports build parameters....

Can you point me some wiki page about those tricks?

I'll see what I can do with the old plugin. When I have something I'll come back to you.

The old plugin is still on SVN, I think we could migrate it to github. Do you want to create now, with the old version as base or do you will create when I have something finished?

Best regards.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/8JR6SMPE8xk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Rui Travassos
Tlm: 96 296 410 4

[Jesse Glick]

On Tue, Aug 12, 2014 at 4:42 PM, Rui Travassos <rui.tr...@gmail.com> wrote:
> Can you point me some wiki page about those tricks?

https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility

> The old plugin is still on SVN, I think we could migrate it to github.

Yes. All the SVN repos got automatically mirrored to GH, but if
switching the authoritative repo it is polite to delete the contents
of the folder in the SVN trunk (replaced with a README noting its new
location).

[Rui Travassos]

Hello,

Finally I had time to finish the plugin. I couldn't make it full compatible with the older version.

I had created a pull request on git hub.

If you merge the code, let me know to prepare the wiki page

Best regards

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/8JR6SMPE8xk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.