[11:36] <jelmer> cjwatson: what is it that powers the CI that e.g. launchpad uses?
[11:46] <cjwatson> jelmer: buildbot.net
[11:46] <cjwatson> jelmer: we don't use that anywhere else though, and will probably eventually move away from it since it's kinda crufty
[11:47] <cjwatson> jelmer: for a bunch of other things we have a complicated pile of Jenkins jobs, which is no better really ... eventually we hope to use Launchpad's newish built-in CI system for this
[12:39] <jelmer> cjwatson: that sounds interesting
[12:39] <jelmer> Would it work for bzr too, or just git?
[12:58] <cjwatson> jelmer: at present just git
[12:59] <cjwatson> adding bzr would probably be possible, though it's mostly hard to justify spending very much time on new features there at the moment
[12:59] <cjwatson> but maybe
[12:59] <jelmer> I might be able to chip in a little, since it seems breezy's current CI will be going away in a while
[12:59] <jelmer> depending on how much work it would be
[13:19] <cjwatson> jelmer: I think it'd basically be changes to lpbuildd.ci and lpbuildd.target.run_ci in launchpad-buildd, a DB patch to RevisionStatusReport and CIBuild in LP, corresponding code patches, something in CIBuildBehaviour, maybe something in the branch scanner to trigger builds, probably bits of UI.  But maybe first look at https://lpcraft.readthedocs.io/ to see whether it's suitable for you (you can 
[13:20] <cjwatson> "snap install lpcraft" and try it out locally)
[13:30] <jelmer> cjwatson: is it ubuntu-specific?
[13:30] <jelmer> (a first glance suggests it is)
[13:32] <cjwatson> jelmer: it doesn't have to be in principle, but at present yes
[13:33] <cjwatson> we've been developing it mainly for a customer project in the first instance, so you know how it is, anything not on the critical path tends to get pushed aside