Let it be no secret that I’m unhappy with the state of VMBuilder in Lucid (and in general for that matter). Way too many regressions crept in and I didn’t have time to fix them all. I still expect to do an SRU for all of this, but every time I try to attack the bureaucracy involved in this, I fail. I need to find a few consecutive hours to throw at this very soon.
Anyways, in an effort to make testing easier, I’ve set up a PPA for VMBuilder.
I’ve set up a cloud server that monitors the VMBuilder trunk bzr branch. If there’s been a new commit, it rolls a tarball, builds a source package out of it, and uploads it to that ppa. That way, adventurous users can grab packages from there and test things out before they go into an SRU. To do this, you simply run this command:
sudo add-apt-repository ppa:vmbuilder/daily
I’m also working on a setup that will automatically test these packages. The idea is to fire up another cloud server, make it install a fresh VMBuilder from that ppa, perform a bunch of tests and report back. To do this, I’m injecting an upstart job into the instance that
- adds the ppa,
- installs vmbuilder,
- builds a VM, which (using the firstboot option) will call back into the host when it has booted succesfully,
- sets up a listener waiting for this callback,
- waits for set amount of time for this callback.
If I get a response in a timely manner, I assume all is well. If not, it’ll notify me somehow.
The idea is to make it run a whole bunch of builds to attempt to exercise as much of the code base as possible.
I’ll try to make a habit of blogging about the progress on this as I know a lot of people are aggravated by the current state of affairs and this way, they can see that something is happening.