|Re: [hudson-dev] General newbie question (projects + job executions)|
Although they might be classed more as opinion than answers.
On 27/03/2012 15:59, Ley, Chung wrote:
We use Hudson project jobs for each component in this case, then each dev team can see there component build and test results by checking there job results. You cna then use artifacts from those component jobs to build larger integration projects that show results of that integration, building up to the logical 'whole thing'. It's slightly harder to architect, although not that hard if you are using maven.
Depending on how you submit to this farm and how the results are reported you could use a Hudson job to submit and wait for the results, although this would block a Hudson executor, it wouldn't massively increase your server load as it would just be waiting. Investigate the build timeout plugin to protect from farm failures etc...
Also have a look at Hudson's ability to fingerprint files in sub-projects and join up test results based on the shared usage of a fingerprinted file.
You can manage these in the same CI and promote builds up through the levels. Have a look at the promoted builds plugin for what you can do. You can streamline the UI by having development, main, and release views that can be used by the different groups, dev, qa, etc...
Back to the top