* Martin Pitt [Thu Jan 23, 2014 at 03:34:42PM +0100]: > Michael Prokop [2014-01-23 15:21 +0100]: > > * Martin Pitt [Thu Jan 23, 2014 at 02:37:17PM +0100]: > > > 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? > > What job scheduler is in use for jenkins.debian.net? > > Are you using zookeeper for jenkins.qa.ubuntu.com? > Jenkins is a job scheduler already AFAIK. Ah, now I get what you mean, I see. :) (FTR: basically you can trigger builds remotely, build periodically or poll the SCM (and of course trigger jobs after other job runs) in Jenkins.) > We have a couple of big iron servers for actually running the > tests (they provide 4 or 8 parallel qemu runs) that are registered > as slaves in Jenkins, and the auto-generated Jenkins jobs from > lp:auto-package-testing, and Jenkins does the rest. Jean-Baptiste > is driving this part. I see, thanks for sharing. When do you schedule those runs? Like before a package enters the archive or after it has already entered the archive? Out of any pipeline? (I'm running autopkgtest test runs as part of the normal binary package builds, also in Jenkins but fully VCS-only driven.) regards, -mika-
Attachment:
signature.asc
Description: Digital signature