Thank you all for the kind and warm words! > 1) Would it be possible to run this on port 80 instead of port 8080?
This is piece of cake by leveraging Docker. Its on 80 now. :) http://ci.bigtop.apache.org/view/Bigtop-trunk/job/Bigtop-trunk-packages/ > 2) Is the setup/configuration of this Jenkins server documented/scripted > somewhere ... Yup, I really should get this done! Sorry I haven't got time to put a polished doc for jenkins setup on our wiki. But I did log down all the steps in my evernote. Should be easy to roll our a version for you. :) And Cos is right, what I've done have nothing to do with ci/jenkins groovy scripts. I don't have time to investigate them because of time limitation set by old CI master retirement... Despite that, I tend to use simple commands for jobs setup in new CI, hence it's not to hard for you to replicate by looking into job definition directly. I'll write details in the doc. Anyhow, I think it's much better to use our gradle system for automation to run any bigtop functions. With this simplicity users won't need to write any hard-to read code in Jenkins commands. Cos, I'm still stuck on BIGTOP-2110, which is to fix packages build random failure. Since you're much familiar to gradle, do you have a better idea to cache gradle packages inside container? Evans 2015-11-03 9:20 GMT+08:00 Andrew Purtell <[email protected]>: > Thanks so much for doing this Evans! > > > On Mon, Nov 2, 2015 at 2:36 PM, Konstantin Boudnik <[email protected]> wrote: > > > Just in case it was missed before, I'd like to thank Evans for this > amazing > > work on our new CI infrastructure > > > > > > > http://ci.bigtop.apache.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-packages/ > > > > OMG! This is so great! I know Evans was doing a lot of it for sure, but I > > want > > to thank everyone who spent time working on this or contributed > otherwise! > > > > Cos > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
