tree b76d3b30613ab9274503c2adc98205fb2f2074ed
parent fe195465f1685da4ffe81d21f4c0d6ea5c58e47a
author Luca Milanesio <luca.milanesio@gmail.com> 1581320876 +0000
committer Luca Milanesio <luca.milanesio@gmail.com> 1592437238 +0000

Do not limit the maximum number of jobs

The maximum number of verification jobs must not be
limited in number but only in time, otherwise the verification
pipeline would stop when there are too many open changes.

This is due to how the Checks integration and API works: once
a change is scheduled for being built is automatically not
returned anymore as pending, causing the job to be considered
as removed. If there are too many open changes and thus too
many removed jobs, the build just started would risk to be
immediately removed because of the automatic mechanism
of discarding old builds.

By removing the limit, prevent that situation to happen.
It will still remove the old builds by time and not by
number of builds anymore.

Change-Id: I68d0b65e015be376420f83ef2ac57373bdb0d44a