diff options
author | 2023-03-22 14:57:21 +0100 | |
---|---|---|
committer | 2023-03-24 12:04:06 +0100 | |
commit | da80f11efeea451eaa00e347f722d867ed9ac5be (patch) | |
tree | 71b8ec73505c85464ac4f06ddde7ea33560eebbc /scripts/coverage/compare_gcov_json.py | |
parent | gitlab-ci: Cover SPICE in the MSYS2 job (diff) | |
download | qemu-da80f11efeea451eaa00e347f722d867ed9ac5be.tar.xz qemu-da80f11efeea451eaa00e347f722d867ed9ac5be.zip |
cirrus-ci: Remove MSYS2 jobs duplicated with gitlab-ci
- Various developers are reluctant to git Cirrus-CI the permissions
requested to access their GitHub account.
- When we use the cirrus-run script to trigger Cirrus-CI job from
GitLab-CI, the GitLab-CI job is restricted to a 1h timeout
(often not enough).
- Although Cirrus-CI VMs are more powerful than GitLab-CI ones,
its free plan is limited in 2 concurrent jobs.
- The GitLab-CI MSYS2 jobs are a 1:1 mapping with the Cirrus-CI ones
(modulo the environment caching).
Reduce the maintenance burden by removing the Cirrus-CI config file,
keeping the GitLab-CI jobs.
Update Yonggang Luo's maintenance file list to the new file, which
use the same environment shell.
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-Id: <20230322135721.61138-3-philmd@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'scripts/coverage/compare_gcov_json.py')
0 files changed, 0 insertions, 0 deletions