[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24764:
-------------------------------
Attachment: two_jobs_in_parallel.png
> 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, 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)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24764:
------------------------------------
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.
> 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
>
>
> {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)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24764 at 9/22/17 1:58 PM:
-------------------------------------------------------------
Here's the diff of what tests ran/skipped, showing only the entries missing from the dev-platform side:
{code}
on fusesource:
0 failures (-7) , 17 skipped (±0)
1,042 tests (-60)
Took 44 min.
on dev-platform:
0 failures (±0) , 6 skipped (±0)
958 tests (-10)
Took 40 min.
Package Duration Fail Skip Pass Total
org.fusesource.ide.jmx.camel.tests.integration.navigator 1m15s 0 0 5 5
org.fusesource.ide.projecttemplates.actions 3.2 sec 0 0 2 2
org.fusesource.ide.projecttemplates.tests.integration.wizards 32 min 0 11 47 58
org.fusesource.ide.projecttemplates.tests.integration.wizards.pages.model 6 ms 0 0 3 3
org.fusesource.ide.projecttemplates.wizards.pages 0.48 s 0 0 7 7
org.fusesource.ide.server.tests.bean 36 ms 0 0 5 5
org.fusesource.ide.server.tests.locator 58 ms 0 0 5 5
{code}
was (Author: nickboldt):
Here's the diff of what tests ran/skipped, showing only the entries missing from the dev-platform side:
{code}
on fusesource:
0 failures (-7) , 17 skipped (±0)
1,042 tests (-60)
Took 44 min.
on dev-platform:
0 failures (±0) , 6 skipped (±0)
958 tests (-10)
Took 40 min.
Package Duration Fail Skip Pass Total
org.fusesource.ide.jmx.camel.tests.integration.navigator 1m15s 0 0 5 5
org.fusesource.ide.projecttemplates.actions 3.2 sec 0 0 2 2
org.fusesource.ide.projecttemplates.tests.integration.wizards 32 min 0 11 47 58
org.fusesource.ide.projecttemplates.tests.integration.wizards.pages.model 6 ms 0 0 3 3
org.fusesource.ide.projecttemplates.wizards.pages 0.48 s 0 0 7 7
org.fusesource.ide.server.tests.bean 36 ms 0 0 5 5
org.fusesource.ide.server.tests.locator 58 ms 0 0 5 5
{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: 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
>
>
> {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)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24764:
------------------------------------
Here's the diff of what tests ran/skipped, showing only the entries missing from the dev-platform side:
{code}
on fusesource:
0 failures (-7) , 17 skipped (±0)
1,042 tests (-60)
Took 44 min.
on dev-platform:
0 failures (±0) , 6 skipped (±0)
958 tests (-10)
Took 40 min.
Package Duration Fail Skip Pass Total
org.fusesource.ide.jmx.camel.tests.integration.navigator 1m15s 0 0 5 5
org.fusesource.ide.projecttemplates.actions 3.2 sec 0 0 2 2
org.fusesource.ide.projecttemplates.tests.integration.wizards 32 min 0 11 47 58
org.fusesource.ide.projecttemplates.tests.integration.wizards.pages.model 6 ms 0 0 3 3
org.fusesource.ide.projecttemplates.wizards.pages 0.48 s 0 0 7 7
org.fusesource.ide.server.tests.bean 36 ms 0 0 5 5
org.fusesource.ide.server.tests.locator 58 ms 0 0 5 5
{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: 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
>
>
> {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)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24764 at 9/22/17 1:20 PM:
-------------------------------------------------------------
So just looking at the org.fusesource.ide.jmx.camel.tests.integration test, I see a much shorter workspace/.metadata/.log file for dev-platform jenkins vs. fusesource. Fusesource has failures, where dev-platform does not.
!fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png|thumbnail!
* [fusesource log|https://issues.jboss.org/secure/attachment/12425180/fusesource__org.f...] vs.
* [dev-platform log|https://issues.jboss.org/secure/attachment/12425179/dev-platform__org...]
These files pulled from here:
* https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To...
* https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... what's going on in the test that there's failures happening in fusesource, but NOTHING is being logged (no errors, anyway) on dev-platform?
was (Author: nickboldt):
So just looking at the org.fusesource.ide.jmx.camel.tests.integration test, I see a much shorter workspace/.metadata/.log file for dev-platform jenkins vs. fusesource. Fusesource has failures, where dev-platform does not.
!fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png|thumbnail!
* [^fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt] vs.
* [^https://issues.jboss.org/secure/attachment/12425179/dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%2520sp%40c%C3%A9_.metadata_.log.txt]
These files pulled from here:
* https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To...
* https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... what's going on in the test that there's failures happening in fusesource, but NOTHING is being logged (no errors, anyway) on dev-platform?
> 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
>
>
> {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)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24764 at 9/22/17 1:18 PM:
-------------------------------------------------------------
So just looking at the org.fusesource.ide.jmx.camel.tests.integration test, I see a much shorter workspace/.metadata/.log file for dev-platform jenkins vs. fusesource. Fusesource has failures, where dev-platform does not.
!fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png|thumbnail!
* [^fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt] vs.
* [^https://issues.jboss.org/secure/attachment/12425179/dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%2520sp%40c%C3%A9_.metadata_.log.txt]
These files pulled from here:
* https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To...
* https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... what's going on in the test that there's failures happening in fusesource, but NOTHING is being logged (no errors, anyway) on dev-platform?
was (Author: nickboldt):
So just looking at the org.fusesource.ide.jmx.camel.tests.integration test, I see a much shorter workspace/.metadata/.log file for dev-platform jenkins vs. fusesource. Fusesource has failures, where dev-platform does not.
!fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png|thumbnail!
* [^fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt] vs.
* [^dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt]
These files pulled from here:
* https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To...
* https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... what's going on in the test that there's failures happening in fusesource, but NOTHING is being logged (no errors, anyway) on dev-platform?
> 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
>
>
> {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)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24764:
------------------------------------
So just looking at the org.fusesource.ide.jmx.camel.tests.integration test, I see a much shorter workspace/.metadata/.log file for dev-platform jenkins vs. fusesource. Fusesource has failures, where dev-platform does not.
!fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png|thumbnail!
* [^fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt] vs.
* [^dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt]
These files pulled from here:
* https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To...
* https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
So... what's going on in the test that there's failures happening in fusesource, but NOTHING is being logged (no errors, anyway) on dev-platform?
> 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
>
>
> {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)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24764:
-------------------------------
Attachment: fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png
> 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
>
>
> {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)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24764:
-------------------------------
Attachment: fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt
> 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
>
>
> {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)
8 years, 6 months