Le 9 févr. 2015 08:13, "Per Arnold Blaasmo" <[email protected]> a écrit : > > 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. >
BTW, I'm quite curious why this is an issue. We also have both Git and subversion repositories here and this is no issue at all. You mean for the same project (meaning same lifecycle, one release, etc.) you can have your sources spanned onto both svn AND Git repositories? -- 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/CANWgJS6B%2BKHun38dqX4BgHFD3LMofVhz2X3Pow5My9zTvPZPCw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
