stopping/aborting obsolete jenkins jobs

[Eli Mesika]

----- 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 
 

> 
> 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
>