[jbosstools-issues] [JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-24764:
-------------------------------
    Attachment: fuse-am3-building-OK.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 at cé_.metadata_.log.txt, fuse-am3-building-OK.png, 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 at cé_.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/Devstudio/view/devstudio_master/job/jbosstools-fuse_master/jobConfigHistory/showDiffFiles?timestamp1=2017-06-21_16-03-25&timestamp2=2017-06-22_18-27-59
> 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)