WDYT about running parallel processes during a Tycho build

running a different job to bootstrap all the runtimes needed by these long-running i-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/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... 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... ? b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?