How do I shot buildserver?
For the longest time I’ve had it on my mind to set up a Kde buildserver which would generate weekly rpm snapshots of trunk for me and a small groups of friends to test the latest trunk and various Fedora packages with minimal hassles.
For the last week or two I’ve been setting up this server; getting a working repo mirror of all my repositories (fedora, updates, kde, kde-testing, kde-unstable) and setting it up to be accessible outside of my LAN. It looks as though my ISP hates me though, and has most ports filtered and the rest have deep packet inspection, etc. All of this is solvable, and will be moot at university, but the actual buildscripts are beginning to be more of a hassle. I need a tools that can automate as much as possible in my setup. Sorting newly added files into the correct subpackages is of course not a task I’d expect any buildsystem to be able to handle but that should happen rarely enough that the builder should only send me an email to let me know and be sufficient. The first and most obvious script that comes to mind is Micheal Pyne’s awesome kdesvn-build, but my perl-fu is probably not enough to hack the features I’d like onto it. 😦 I know that buildsystems like these have to be fairly common, but I haven’t really found anything that fits my needs:
- Update various svn and git repositories and spin tarballs of them.
- Reposync my local repositories.
- Update a spec file to point to these tarballs and update the Version: tag.
- Generate an srpm for each package.
- Fire said srpm at a local mock or koji instance.
- Make sure builds are successful.
- Toss what is completed into a local repo.
- Mail log files of failed builds to me.
- Run createrepo on the final repository.
Annnnnd the floor is open!
Powered by Blogilo