Hi, SVN Merge plugin is pretty close to what I need, but it seems to rely on creating branches and merging. For git, branches are lightweight, so creating and deleting branches is no big deal. For Subversion, branches are a bit more heavyweight, and for certain projects like FreeBSD, creating lots of branches in Subversion doesn't fit with the existing workflow.
Submitting a patch, and compiling and testing the patch is closer to how FreeBSD uses Subversion. The other workflow that I was thinking about was to use git-svn to clone the Subversion repo via git, then create a lightweight branch in git, then do the build/test, and then do a git-svn dcommit back to Subversion only if the build/test passes. Has anyone implemented that type of workflow? -- Craig On Fri, Nov 7, 2014 at 7:08 PM, Jesse Glick <[email protected]> wrote: > Did you try the SVN Merge plugin? I am not sure how well maintained it is > but it is probably the closest to what you are looking for. > > -- > 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. > -- 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.
