On Sat, Nov 8, 2014 at 9:09 PM, Craig Rodrigues <[email protected]> wrote: > 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.
Unfortunately as Subversion is not a DVCS there can be no equivalent of the “gate repository” trick used by the Jenkins Enterprise plugin. You could have people submit patches rather than true commits and have Jenkins create the commit, as e.g. Team City does, but this seems rather fragile when you consider multiple developers, multiple concurrent changes, file renames & deletes, etc. -- 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.
