9968de0a4a
On the primary QEMU repository we want the CI jobs to run on the staging branch as a gating CI test. Cirrus CI has very limited job concurrency, so if there are too many jobs triggered they'll queue up and hit the GitLab CI job timeout before they complete on Cirrus. If we let Cirrus jobs run again on the master branch immediately after merging from staging, that just increases the chances jobs will get queued and subsequently timeout. The same applies for merges to the stable branches. User forks meanwhile should be allowed to run Cirrus CI jobs freely. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Reviewed-by: Thomas Huth <thuth@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> Reviewed-by: Willian Rampazzo <willianr@redhat.com> Message-Id: <20211116112757.1909176-1-berrange@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> |
||
---|---|---|
.. | ||
cirrus | ||
custom-runners | ||
edk2 | ||
opensbi | ||
buildtest-template.yml | ||
buildtest.yml | ||
check-dco.py | ||
check-patch.py | ||
cirrus.yml | ||
container-core.yml | ||
container-cross.yml | ||
container-template.yml | ||
containers.yml | ||
crossbuild-template.yml | ||
crossbuilds.yml | ||
custom-runners.yml | ||
edk2.yml | ||
opensbi.yml | ||
qemu-project.yml | ||
stages.yml | ||
static_checks.yml |