Slightly related to T225231
Currently, there's no way (a quick google suggests the only real ways involve killing everything) to kill all jobs for a revision/patch from zuul before it hits jenkins. At best, you wait until it does, then abort the builds (not ideal)
Declining, the feature request is a bit unclear. The jobs got triggered for a reason they are waiting for a free slot. If there is a use case for not running them, we should address that in the Zuul workflow.
Currently, there's no way (a quick google suggests the only real ways involve killing everything) to kill all jobs for a revision/patch from zuul before it hits jenkins. At best, you wait until it does, then abort the builds (not ideal)
You can't stop stuff queued in zuul, until the individual jobs are spawned to CI and then kill them individually
Just because something is in the queue, doesn't mean we actually want to run it
What I was saying is that we should filter out those jobs before they get put in the queue. Once they are in the queue, surely we want to have them running.