[
https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13411:
------------------------------------
[~maxandersen] Would it not make sense to have that repo branched so that work for
specific streams (Juno, Kepler, Luna) can be done in the right place? It's not like we
can't spawn more jobs and more update sites, one per stream/branch.
[~mmalina], [~ldimaggio] Should jbosstools-integration-tests be branched to support at
least Juno and Kepler tests for now (Luna next year), so that the integration tests
currently in the JavaEE project's master branch can be offloaded to the
integration-tests repo's master (Kepler) branch? (See also JBIDE-13796.)
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/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?
--
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