[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

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-13411:
---------------------------------------

[~maxandersen] We don't use multiple versions of RedDeer anymore. But right now we still use a floating version in both 4.0.x and master streams (nightly build of RedDeer). In a few weeks, RedDeer tests should be fixed and version 0.2 should be released. And then we'll move that to a stable location and use it in at least 4.0.x branch of jbosstools-integration-tests so it's not moving anymore.

[~nickboldt] jbosstools-integration-tests are already branched like this - right now we have branches jbosstools-4.0.x (Juno) and master (Kepler). Once we start testing Luna, we will branch jbosstools-4.1.x and master will become the playground for Luna.

I am not quite sure how this would work with the JavaEE test being moved to jbosstools-integration-tests. Right now all of the tests are owned by us (QE). These tests would continue to be owned by JavaEE component dev team, right? As it is now, we cannot reliably just run the whole set of the integration tests in Jenkins - each member needs to take care of his test and make sure he runs it correctly and then also interpret the results. So if you just added the JavaEE integration tests (which I'm not sure which tests these are actually) to jbosstools-integration-tests to be run as part of the jenkins build of the jbosstools-integration-tests update site, you wouldn't see very clearly if those JavaEE tests are passing or not. One way would be to have a separate job to run just these JavaEE tests from jbosstools-integration-tests repo (once they're moved there).
                
> 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: Build/Releng, Visual Page Editor Templates
>    Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Denis Golovin
>            Priority: Blocker
>             Fix For: 4.1.x
>
>         Attachments: tests-vs-tycho-build-time.png
>
>
> 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