On 06. feb. 2015 16:41, Craig Rodrigues wrote: > > > On Fri, Feb 6, 2015 at 5:22 AM, Jesse Glick <[email protected] > <mailto:[email protected]>> wrote: > > > Probably this and other issues in multiple-scms are not really > fixable, given the design of the SCM interface. My recommendation is > to avoid that plugin, and if you need multiple checkouts in one build, > use Workflow which supports this natively. > > > > I can't speak for Per Arnold Blaasmo, but at least for me, I > have a *lot* of Jenkins jobs using Multiple SCM's plugins, so > migrating to Workflow off the bat would be nontrivial. > This is not good news for me either :-(
We have two main repo types in the company, Subversion and Git. And though many are using and migrating to Git, there will be a dependency to subversion for a long time yet. Jesse, can you elaborate some more on the problems with the design of the SCM interface that gives the problems with the multiple-scm plugin? Maybe I can get someone to look into it? Regards Per A. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/54D85E2E.9060405%40atmel.com. For more options, visit https://groups.google.com/d/optout.
