StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPossible solutions for using TFS and SVN in multiple vendor projects?
text
Body
copied!<p>I'm working to establish a source control solution that will allow multiple vendors to contribute to a single project (multiple Sitecore CMS sites in a single installation). Ideally we'd like to go with TFS as it seems to fit our in-house requirements and support best. Some of our vendors, however, prefer SVN. If we choose to go with TFS there seem to be a number of possible solutions to this.</p> <p>1) Vendors commit to using TFS directly, using MS tools and CALs(e.g. Visual Studio for back end devs and tfs.exe etc for front end).</p> <p>2) Vendors use TFS, plugging in with and adaptor to their current SVN tools (SVN Bridge / SVN Tortoise) - still requires a CAL per developer.</p> <p>3) Vendors use a single CAL to establish a codebase from the TFS which they then use as an SVN repository. Vendors use SVN locally but use continuous integration between the SVN repository and the TFS to keep in synch.</p> <p>The third option looks cheaper in licensing terms, but would add considerable complexity and developer time in the synching, and would presumably lose check-in info on a per developer basis (a single dev would check in all changes by his team to the TFS).</p> <p>We don't actually need a great level of detail and sophistication, just basic functionality. The vendors are responsible for their teams, we don't even really need to know who did what at that level, just that it came from vendor A or vendor B.</p> <p>What are the relative drawbacks and benefits of the approaches above, and what tools would make my life easier?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload