Automated stage building with Jenkins
For quite some time now, I’ve been working on the automatic creation of Exherbo stages for AMD64 (x86_64) and X86 using Jenkins.
Till now, Exherbo’s stages were created manually by one of us Exherbo core developers and usually basically “on-demand” or when they were major changes. This finally changed yesterday.
Using the jobs stage_amd64 and stage_x86 respectively, the stages…
- are built using a modified stage building script – each stage is build from scratch. The latest stage gets unpacked and used to build a new one. I call this: Implicit pro-active quality assurance. No pbins are used in the entire process. Everything is fresh and new, just for you.
- the sources are kept right next to the stages at https://galileo.mailstation.de/stages/sources. You can see right there what sources were used.
- the XZ archive is added to the job (the most recent ten stage archives are kept on their respective job). Like this, you can always check the exact build log for the stage you want and rest assured both are right there at your fingertips.
- next, the successfully built stage is deployed to https://galileo.mailstation.de/stages/. exherbo.org is undergoing maintenance but you really want your Exherbo? Download a stage from this alternative location, sync your repositories from Gerrit and you’re unstoppable!
- and finally automatically transferred to our traditional http://dev.exherbo.org/stages/ where some “extra magic” is performed by Jenkins that creates the “current” symlinks, updates the checksum files, etc.
And this happens every single day. The entire process is completely scalable as well – once the cross stuff is production-ready, I’m going to build ARM stages as well and it will be done by simply copying a Jenkins job and changing a few lines. A milestone for Exherbo.
We just made major changes? Wait a few hours, get them in your stage for your new Exherbo installation.
You somehow got a broken stage? Use an older one, compare them, go nuts with them. There are always at least 10 stages per architecture to choose from.
And if a stage fails to build? Well, the next day it will be fixed because we’re watching over the entire process.
Isn’t this incredibly awesome?
And you can even play a round of Bullshit Bingo using this very post! 😉
|I am and have been working on quite a few F/OSS projects:|
3 thoughts on “Automated stage building with Jenkins”
This really is awesome. Bullshit or not.
Thank you for your great work on Exherbo!!
really i’d love to see the JENKINS-ci in github.
I’m not quite sure what exactly you’re referring to:
– Jenkins itself is hosted on github: https://github.com/jenkinsci/jenkins/
– The scripts I’m using are hosted in git on my own server: https://galileo.mailstation.de/cgit/cgit.cgi/jenkins-build.git/
The scripts won’t be moved to github but are accessible via anonymous cloning.
Let me know if I misunderstood your comment.