I'm not sure to understand you thoroughly, but wouldn't a multimodule project + activating hudson incremental build be the solution?
Cheers 2010/9/23 Thomas Sundberg <[email protected]> > Hi! > > We have a Maven project that we want to build parts of using Hudson. Our > setup is similar to this: > > A -- B > +- D > +- E > +- F > > Where A, B, C, D, E and F are maven modules. A is parent to all modules, D > is parent to E and F. > > We are using profiles that are defined from module A and down in order to > minimize configuration. > > We have a profile defined in module A with the name Foo. Foo is also > defined > in module D and finally in module E with narrower and narrower properties. > This works ok for us. > > I have a Hudson CI server with a job defined for each module B, E and F. > Each job listens for changes at the level A. > > I would want my Hudson to listen to module F and if a change is found, > checkout from module A and run a Maven build on module F. The reason is > that > I need all profile settings, from A and downwards, during the execution of > module F. Each execution takes a couple of minutes and there are many jobs. > > I have looked at the configuration options in Hudson and I can't see that > this is possible. > > Do you have any suggestions for a solution? > > /Thomas > > -- > Thomas Sundberg > M. Sc. in Computer Science > > Mobile: +46 70 767 33 15 > Blog: http://thomassundberg.wordpress.com/ > Twitter: @thomassundberg > > Better Software Through Faster Feedback > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
