Hi Gregor, awesome! I think you can use the Jenkinsfile from my fork[1] as a starting point. Looking at it I remembered that I wanted to have Java 8/9 build run in parallel, and that complicates the build as two checkouts are needed (for two nodes).
If you'd like to start from a fresh, that's also OK, there are a couple of titbits that I found when looking at the jobs currently defined on builds.apache.org like: - use of specific local repository (/home/jenkins/jenkins-slave/maven-repositories/0) - use of Maven profiles and properties (I fiddled with that a bit), we have `notest` (`fastinstall` profile) and `fulltest` jobs currently, both have `-Dnoassembly` property set I think we can start with a basic Jenkinsfile test it in parallel while we build up confidence and then tweak it as needed, not sure if Christian managed to give us job configuration access on builds.apache.org, but I think Claus can create new jobs, right? zoran [1] https://github.com/zregvart/camel/blob/jenkinsfile/Jenkinsfile On Tue, Nov 7, 2017 at 10:24 AM, Gregor Zurowski <gre...@list.zurowski.org> wrote: > Hi Zoran, > > It would be great if we could switch to the Jenkinsfile approach soon. > I'd be available to help with this. :) > -- Zoran Regvart
