Not sure if we can leverage travis to do this kind of work. As camel build is a little bit longer one by one, if we can run the component tests in parallel that you could save us lot of time.
Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thu, May 10, 2018 at 6:15 AM, Zoran Regvart <zo...@regvart.com> wrote: > Hi Cameleers, > so it's not that bad[1] 77 tests failed in total. I think we need to > play with opening up some modules a bit. I'm a bit sad that it takes 9 > hours for the job to run, when we add JDK 11 I would expect it to take > 13 hours, would be nice if there was a way to just run the tests in > parallel on multiple JDKs. > > zoran > > [1] https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.daily/ > lastCompletedBuild/testReport/ > > On Wed, May 9, 2018 at 11:45 AM, Zoran Regvart <zo...@regvart.com> wrote: > > Hello Cameleers, > > I've created a build that will run once every day to run tests on JDK > > 9 and 10[1], the configuration for the build is in > > `Jenkinsfile.daily`[2]. > > > > Suggestions and contributions are welcome :) > > > > zoran > > > > [1] https://builds.apache.org/view/A-D/view/Camel/job/Camel.daily/ > > [2] https://gitbox.apache.org/repos/asf?p=camel.git;a=blob; > f=Jenkinsfile.daily;hb=HEAD > > -- > > Zoran Regvart > > > > -- > Zoran Regvart >
