[jbosstools-dev] Please take care of CI job for your component!

[Nick Boldt]

Not sure... you tell me:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stable_branch.component--cdi/buildTimeTrend 
(3.3.x branch)

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_trunk.component--cdi/buildTimeTrend 
(trunk)


On 08/30/2012 03:02 PM, Alexey Kazakov wrote:
> On 08/30/2012 11:41 AM, Nick Boldt wrote:
>> If you spread the 25 components out in approximate order, assuming
>> that no two run in parallel (which is of course not the case but makes
>> it easier to estimate times) then a fresh CDI build is over 9 hours
>> after a fresh usage, tests, or common build. Since CDI has over an
>> hour of tests in it, Seam is therefore close to 12 hours down the stack.
>
> An hour for CDI tests? Why so long? It takes ~ 11 minutes (about 1000
> JUnit tests) with Tycho on my laptop.

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com