Need production-devel builder

I've marked this as critical because I think it would be quicker to fix this and then land to production-devel than to continue as we are. Or, to put it another way, there should be no more landings to production-devel until this bug is fixed.

I believe this is blocked until the method that's used to built the source tree on buildbot can deal with specific revision numbers of source code branches rather than the tip of each one.

Tom is right. Launchpad now supports specifying revision numbers for sourcecode branches, but we need to change buildbot and ec2 scripts to take advantage of it. That should be much easier now.

The LOSA aspects of this work are being tracked in:
  https://rt.admin.canonical.com/Ticket/Display.html?id=37189

Gary, I think buildbot and ec2 scripts already use update-sourcecode which supports specific revisions. So that work is done, AFAIK. Do you know any other changes required?

I've created a new AMI. It would need:

valid_ami_location_regex=r'.*/lpbuildbot-slave-production-devel-(\d+)',

It uses the same password as the other current production slaves. If someone could create and propose a branch that DTRT for buildbot then we should be good to go - then it's just a case of use changing the PQM config for the production-devel codeline to not run the test suite, and setting up the buildbot-poller to do it's thing for production-devel -> production-stable - this is managed in the same branch, so one branch proposal should be able to cover both.

Tom, I've updated the lpbuildbot branch with the regex and password, but haven't done the PQM stuff. TBH, I don't know where to start there right now.

This has now been setup. Just waiting for a test commit to make it through the system before we declare success.

Hurrah, it works!