stopping/aborting obsolete jenkins jobs

[David Caro]

On 05/05, Eli Mesika wrote:
> 
> 
> ----- Original Message -----
> > From: "Yedidyah Bar David" <didi at redhat.com>
> > To: "Infra" <infra at ovirt.org>
> > 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?
> 
> 
> Happens to me a lot 
> I think that it should be automatic and if you are pushing version x+1 then if version x jobs are still running , it will be aborted 


Afaik, that behavior is only supported by zuul. So not something that we can
easily change.
>  
> 
> > 
> > This will both give quicker results for the dev/maint and lower the load on
> > the
> > slaves.
> > 
> > Best,
> > --
> > Didi
> > _______________________________________________
> > Infra mailing list
> > Infra at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> > 
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dcaro at redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20150505/6a1e0149/attachment.sig>