[jbosstools-issues] [JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750114#comment-12750114 ] 

Mickael Istria commented on JBIDE-13411:
----------------------------------------

> WDYT about running parallel processes during a Tycho build

Actually I never tried it. That could be a solution if we can ensure tests are really independent and can actually run in parallel. I'm not sure it's really possible when it come to UI tests

> running a different job to bootstrap all the runtimes needed by these long-running i-tests?

That sounds better. Continuous Integration us requires a fast feedback loop to be efficient, the test run in continuous build should be a compromise between acceptance and fast execution. Several hours are way to much, and it seems to me that most of those tests are redundant, on version of Seam runtime changes.
I would suggest we run only 1 test suite (for let's say, the latest version of Seam runtime) as part of the continuous build, and we create a new job for the other tests.
                
> JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13411
>                 URL: https://issues.jboss.org/browse/JBIDE-13411
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Visual Page Editor Templates
>    Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Yahor Radtsevich
>            Priority: Blocker
>
> On a good day, tests will run and all pass in under 4hrs.
> On a grey day, tests will have failures but complete in under 6hrs.
> On a bad day,  tests will stall out and the job will fail when it hits its duration upper limit of 8hrs.
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--javaee/buildTimeTrend
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.1_trunk.component--javaee/buildTimeTrend
> Surely some of these tests are:
> a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.integrationtests.aggregate/ ?
> b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira