I'm going to take a wild stab in the dark and guess that you are using the "Maven" project type...
Don't use the "Maven" Project type. It is soooooo not the Maven way.... it messes with your build behind your back... the build it runs is not the same as a build from the CLI or a build with the FreeStyle project type. Use the FreeStyle project type.... it's the only one I use....* -Stephen *unless my employer's customers have a bug in the "Maven" project type** **in case any customers are reading this mailing list On 3 October 2011 10:27, Miguel Almeida <[email protected]> wrote: > > Dear all, > > I am running the goals "site:site site:deploy" on the same Maven run inside > my Jenkins CI system. The idea is to run this daily and then SCP the results > to another location. > > My site plugin is configured to run the cobertura report configured with > aggregate=true: > a) make reports of every module in the project > b) generate a global report in the parent. > > The order must be this, because the aggregate report is the sum of the > reports of individual modules. > > However, if I run site:site site:deploy, the order will be: > Parent - site:site > Parent - site:deploy (because modules are forked and Parent site:site is > quick) > ModuleA - site:site > ModuleB - site:site > > > So the Parent cobertura report the job is deploying is still incomplete. It > should only site:deploy after *every* module's site:site goal has run. > > Do you know how I can run these two goals simultaneously and have the correct > Cobertura result? > > Thank you in advance for your input, > > Miguel Almeida --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
