On Thu, Jan 23, 2014 at 02:37:17PM +0100, Martin Pitt wrote: > Hey Antonio, > > I suppose you BCCed me as I don't usually get WNPP bug mail; thanks! > > You are probably aware that we do this kind of thing in Ubuntu [1], > which spawned quite a bunch of autopkgtest additions and also failures > [2] in Debian. We currently use some wrapper scripts around > autopkgtest [3] and let the whole thing run in Jenkins; that thing has > grown "organically" (to say it in a positive way), but it has a couple > of restrictions and is a bit too complex for my taste. (And that > doesn't even include the integration with britney) > > Since then autopkgtest itself grew a few things which reduces the need > for wrapper scripts (just today I landed some new features particulary > for your use case). So, if you find something which adt-run itself > should do but doesn't, please don't hesitate to file a bug and/or grab > me on IRC (pitti on Freenode). cool, thanks! I think we should absolutely work together and I will bug you with bug reports and whatnot. :) > I'm very eager to see what you have in mind for debci. I think if we > work together and I maybe get to add a proper adt-virt-qemu [4] some > day, we can eliminate [3] entirely, and the whole thing would be > reduced to scanning the archive and scheduling/running adt-run on the > slaves (QEMU, LXC, or schroots in practice). Do you want to use an > existing job scheduler like http://jenkins.debian.net, or perhaps > something simpler like zookeeper? So what debci does ATM is exactly only scanning the archive and calling out to "something" to run the tests. That something now is just `adt-run ... --- adt-virt-schroot` so I need some extra code to make sure the used chroot is up to date etc. My next step is much probably to extract the backend and make it pluggable, so that you can still use schroot, but also submit jobs to jenkins.debian.net. -- Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: Digital signature