[devops] optimize fuel-ci queue handling

[Aleksandra Fedorova]

When patchset comes to the queue at Fuel-CI, all the previous patchsets with the same change_id should be removed from the queue.

[Bogdan Dobrelya (bogdando)]

Consider the manual trigger as well.
E.g. "CI no test" comment should abort CI jobs for given patch set, if any

[Bogdan Dobrelya (bogdando)]

2nd use case is to ensure the trivial rebases would never trigger a CI jobs, if the patchset already has a +2 or more. But it should, if there are at least one -1 exist...

[Andrew Woodward (xarses)]

to the original issue, yes we need to remove previous patch sets in the ci queue. However we reuse change-id when we backport, so we should also check branch.

To Bogdan, all aborted CI should result in CI voting -1

[Aleksandra Fedorova (bookwar)]

Openstack Infra has no workaround for the queue updates. They use zuul for those.

But we can create 'cleanup' job for every Gerrit event. It will go through the current queue and abort all the jobs with the same branch and change_id.

[Aleksandra Fedorova (bookwar)]

Gerrit Trigger plugin now has the "Build Current Patches Only" option which cancels jobs fro previous patchsets of the same change. Let's try it.

[Aleksandra Fedorova (bookwar)]

Seems to work