[
https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-24764 at 9/22/17 4:07 PM:
-------------------------------------------------------------
Latest speculation: maybe we're having issues because slaves are being used for more
than one concurrent build, and the fuse tools build doesn't like to share. Only
example seen so far of a rhel7-devstudio-releng slave being used for parallel jobs is this
one, which shows a flyweight and a real job started in parallel. No proof yet of a fly- or
real-weight job being run in parallel with jbosstools-fuse_master.
!two_jobs_in_parallel.png|thumbnail!
If flyweight jobs are in fact to blame here, I can prevent flyweights that run matrixes
from running on rhel7-devstudio-releng.
Or, we could play around with concurrent build throttling but this isn't something in
use on fusesource jenkins so might be a waste of time:
!throttle-concurrent.png|thumbnail!
was (Author: nickboldt):
Latest speculation: maybe we're having issues because slaves are being used for more
than one concurrent build, and the fuse tools build doesn't like to share. Only
example seen so far of a rhel7-devstudio-releng slave being used for parallel jobs is this
one, which shows a flyweight and a real job started in parallel. No proof yet of a fly- or
real-weight job being run in parallel with jbosstools-fuse_master.
!two_jobs_in_parallel.png|thumbnail!
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:
dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt,
fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png,
fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png,
fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt,
throttle-concurrent.png, two_jobs_in_parallel.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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)