]
Nick Boldt commented on JBIDE-24764:
------------------------------------
After using the new settings.xml and updating the job to look nearly the same as the
fusesource version we get ... the same test failures.
{code}
17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test
(default-test) on project org.fusesource.ide.projecttemplates.tests.integration: An
unexpected error occured while launching the test runtime (return code 137). See log for
details. -> [Help 1]
17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test
(default-test) on project org.fusesource.ide.jmx.camel.tests.integration: An unexpected
error occured while launching the test runtime (return code 1). See log for details. ->
[Help 1]
17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test
(default-test) on project org.fusesource.ide.server.tests: An unexpected error occured
while launching the test runtime (return code 137). See log for details. -> [Help 1]
17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test
(default-test) on project org.jboss.tools.fuse.ui.bot.tests: An unexpected error occured
while launching the test runtime (return code 137). See log for details. -> [Help 1]
{code} --
migrate fusetools job from fusesource jenkins to dev-platform
jenkins
---------------------------------------------------------------------
Key: JBIDE-24764
URL:
https://issues.jboss.org/browse/JBIDE-24764
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Affects Versions: 4.5.0.Final
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.5.1.AM3
Attachments: fuse-master-job-on-dev-platform-jenkins.png,
fuse-master-job-on-fusesource-jenkins.png
{quote}
Lars reenabled it
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
We are still using the one on fusesource jenkins right, it is the only place we have a
"controlled job"
for the migration to dev-platform, I don't know. Lars decided with you (?) (someone
from Jboss tools team) to move to this CI
don't know exactly pros and cons, Lars reported the advantages:
* more slaves
* faster
* easier to manage with the other JBoss Tools job
the issue is that it is not working:
* our tests are failing too often when starting from a empty .m2 repository because some
corrupted jars are downloaded
* one test is failing
* and a third issue now seems that it goes into timeout{quote}