01-20-2011, 09:03 AM
I have been working on a BuildBot for Nightingale (similar to what Songbird currently has) for the purposes of Continuous Integration testing and some form of semi-regular build system. My goal with this is to be able to test and build Nightingale on everything we support, which I expect will be a variety of GNU/Linux-based systems and both 32- and 64-bit systems. It could probably include automated packaging of the builds for different distros as well.
So far I have CI going; the BuildBot instance is currently running on a personal server I set up for it at http://ngale.jackgrigg.com/ (I would assume that a Nightingale domain would be used eventually e.g. http://buildbot.getnightingale.com/ ). There is also an IRC bot that can monitor and control the builders (ngalebuilder on #nightingale). At present it uses the Nightingale source but the Songbird 1.8 dependency tree, since stevo isn't quite finished with the Nightingale one but that will be changed when he is done (which will be VERY handy - to anyone outside POTI the Songbird SVN repos are slow as hell @_@). I have just started on the actual building and packaging part.
So anyway, I'm posting this for two reasons:
So far I have CI going; the BuildBot instance is currently running on a personal server I set up for it at http://ngale.jackgrigg.com/ (I would assume that a Nightingale domain would be used eventually e.g. http://buildbot.getnightingale.com/ ). There is also an IRC bot that can monitor and control the builders (ngalebuilder on #nightingale). At present it uses the Nightingale source but the Songbird 1.8 dependency tree, since stevo isn't quite finished with the Nightingale one but that will be changed when he is done (which will be VERY handy - to anyone outside POTI the Songbird SVN repos are slow as hell @_@). I have just started on the actual building and packaging part.
So anyway, I'm posting this for two reasons:
- To let you all know it's there, and that CI testing appears to be working - the only failing unit test at present is that it can't find the alsa plugin for gstreamer (though this is using the SB internal dependencies) and the release build manifest check fails because the binaries are renamed.
- We will need a variety of computers to have as buildslaves, and preferably they would have heads - I have been running the buildslave on my same personal server so far with Xvfb providing the required display, but given that no one is likely to be using Nightingale on a VPS, I think desktops are probably more appropriate for testing =)