Re: stopping/aborting obsolete jenkins jobs

From: "Eyal Edri" <eedri(a)redhat.com&gt; To: "Yedidyah Bar David" <didi(a)redhat.com&gt; Cc: "Infra" <infra(a)ovirt.org&gt; Sent: Tuesday, May 5, 2015 10:19:57 AM Subject: Re: stopping/aborting obsolete jenkins jobs ----- Original Message ----- > From: "Eyal Edri" <eedri(a)redhat.com&gt; > To: "Yedidyah Bar David" <didi(a)redhat.com&gt; > Cc: "Infra" <infra(a)ovirt.org&gt; > Sent: Tuesday, May 5, 2015 10:15:21 AM > Subject: Re: stopping/aborting obsolete jenkins jobs > > > > ----- Original Message ----- > > From: "Yedidyah Bar David" <didi(a)redhat.com&gt; > > To: "Infra" <infra(a)ovirt.org&gt; > > Sent: Tuesday, May 5, 2015 8:26:43 AM > > Subject: stopping/aborting obsolete jenkins jobs > > > > Hi, > > > > It happened to me quite a lot lately, that I pushed a new patchset for a > > change, > > before jenkins finished running relevant jobs for previous patchsets, in > > some > > cases > > even before it started running some of them. > > > > Perhaps in such a case we should stop (if running) or disable/abort (if > > not > > yet > > running) all the jobs except for the ones running for the latest > > patchset? > > not sure its possible, but its not something that you want to do > (aggressive interrupt jenkins running or queue) > > > > > This will both give quicker results for the dev/maint and lower the load > > on > > the > > slaves. > > > > we are working on improving this on 2 fronts: > 1. adding more slaves > 2. reducing job running time (findbugs is currently being optimized) forgot one more thing - we added a new flag called 'workflow' which we are testing now on the jenkins project. this flag means that the developer marks: "my code is ready for review" (might not be verified yet, since he wants early engagement before running a verification). For jenkins it means that only when a developer will mark +1 on this patch the jenkins jobs will start running on it (instead of running per patchset). so if we're OK in adding this flag to engine/vdsm - it will reduce dramatically the amount of running jobs.

> > and you're welcome to join the effort of getting there next monday, on the > infra hackathon :) [1] > > [1] > https://docs.google.com/spreadsheets/d/1PGGqI5tT_pmF7HUdg63FlozuVoQOBQaO-... > > > Best, > > -- > > Didi > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > > _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra