Migrating from SVN to Git, using Atlassian's Stash. Parent project has 80+ modules. To granularize access to specific modules within this parent project (for outside team module customization requirements), we now have the 80 modules at the 'repository' level. Doing this type of setup, we now have to change our Jenkins build project from 1 SVN 'checkout' from trunk, to using the Multi SCM plugin and having 80+ GIT clones. Is anyone else doing this type of setup? What is the performance impact? What type of overhead issues are you experiencing with this setup?
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.