The listing of jobs is serialized for the console log by jenkins. The
child jobs themselves are already triggered in parallel. The console
log does not make this obvious, but if you watch the live jenkins jobs
queues, you'll see all of the ${project}-${series}-${arch}-ci jobs
running. Hope this answers your question.Francis On Sun, Nov 3, 2013 at 12:26 AM, Evan Dandrea <[email protected]> wrote: > On 30 October 2013 17:53, Thomi Richards <[email protected]> wrote: >> I've just realised that the CI system runs each test configuration in >> series. For example, this job: >> >> http://s-jenkins:8080/job/ubuntu-ui-toolkit-ci/1131/console >> >> runs the trusty-amd64 configuration, and waits for it to end. Then it runs >> the armhf configuration, and waits for it to end... you get the picture. > > Thanks for bringing this to our attention, Thomi. > >> Do you think we could parallelise this? It seems like it might be a simple >> change that would drastically improve the speed of CI runs when hardware >> availability is not the bottleneck. > > Hi everyone, > > Can someone speak to how feasible this is? > >> On a related note, I'm not sure what to do with "bug/feature reports" like >> this in the future. Is there a mailing list I should be sending this to, or >> am I doing the right thing by emailing you? > > You can either file a bug: > https://bugs.launchpad.net/ubuntu-ci-services-itself/+bugs > > Or mail [email protected]. > > -- > Mailing list: https://launchpad.net/~canonical-ci-engineering > Post to : [email protected] > Unsubscribe : https://launchpad.net/~canonical-ci-engineering > More help : https://help.launchpad.net/ListHelp -- Francis Ginther Canonical - Ubuntu Engineering - Continuous Integration Team -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
