I would suggest the following: - One jenkins job for each submodule, allow the jobs for each module to run the unit tests for each module to ensure the gerrit change is good to go - Another jenkins job for each supermodule. This jenkins job would poll for every commit in the supermodule and build them as they happen.
I see a big flaw with this strategy that each submodule gerrit change would need to be merged into the respective submodule before integration testing could occur with the supermodules. I'm not sure what other possible solutions could be. I will be looking into implementing something like this soon (in the next quarter), so will try to update you about my progress. -Joel On Friday, July 6, 2012 4:47:02 AM UTC-6, Karsten Dambekalns wrote: > > Hi Rens. > > On 02.07.2012, at 20:31, Rens Admiraal <rens.admir...@gmail.com> wrote: > > I'm searching for a while now for a solution to use continues > integration in a good way. I'm using a (base) repository which contains the > base structure for my application, and furthermore a lot of git submodules > pointing to repositories containing the packages used in my project. > > It seems we are the only ones doing that… or not? Consider this mail a > "ping" for this thread, and a plea for feedback - even if it's only "we > need more details to provide hints on that one" :) > > Regards, > Karsten
