Hello, I'm just wondering how people with a decent collection of modules are organizing their modules and repositories? We currently have one big repository with everything in it, and three branches, basically stuff moves alpha -> beta -> production. This is nice and simple in a way, but has some obvious and not so obvious downsides.
For one updating a module means going to the "next" branch and doing a checkout of that specific module from the previous branch so as to not just yank in every change made in the previous branch. This along with having just one big commit history for everything makes the git history pretty much useless. And we're now in the process of implementing Jenkins for CI, the lack of granularity is making this a bit of a headache(though this could very well be because we're complete newbies at Jenkins ;) . For example having a post-receive hook triggering a build in Jenkins, with one big repo this will trigger rebuilds of every module since they all subscribe to the same repo even though they're separate jobs. So, how are you people who have actually done this for a while managed this little problem? Separate repos per module? Something else we haven't thought of? Regards Johan -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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/puppet-users/83ae6a7a-b372-408a-b143-8f00f8fdcafb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
