Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-24243 migrate Fuse Tools builds to JBT infrastructure/process
  3. JBIDE-24764

migrate fusetools job from fusesource jenkins to dev-platform jenkins

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • 4.5.1.AM3
    • 4.5.0.Final
    • build
    • None
    • devex #132 May 2017, devex #139 October 2017

      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

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: