Since v2: - Fixed ARM Xen job - Renamed jobs with -$accel trailer (Thomas) Since v1: - Documented cross_accel_build_job template (Claudio) - Only add new job for s390x (Thomas) - Do not add entry to MAINTAINERS (Daniel) - Document 'build-tcg-disabled' job is X86 + KVM - Drop the patches with negative review feedbacks Hi, I was custom to use Travis-CI for testing KVM builds on s390x/ppc with the Travis-CI jobs. During October Travis-CI became unusable for me (extremely slow, see [1]). Then my free Travis account got updated to the new "10K credit minutes allotment" [2] which I burned without reading the notification email in time (I'd burn them eventually anyway). Today Travis-CI is pointless to me. While I could pay to run my QEMU jobs, I don't think it is fair for an Open Source project to ask its forks to pay for a service. As we want forks to run some CI before contributing patches, and we have cross-build Docker images available for Linux hosts, I added some cross KVM/Xen build jobs to Gitlab-CI. Cross-building doesn't have the same coverage as native building, as we can not run the tests. But this is still useful to get link failures. Resulting pipeline: https://gitlab.com/philmd/qemu/-/pipelines/226240415 Regards, Phil. [1] https://travis-ci.community/t/build-delays-for-open-source-project/10272 [2] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing Philippe Mathieu-Daudé (5): gitlab-ci: Document 'build-tcg-disabled' is a KVM X86 job gitlab-ci: Replace YAML anchors by extends (cross_system_build_job) gitlab-ci: Introduce 'cross_accel_build_job' template gitlab-ci: Add KVM s390x cross-build jobs gitlab-ci: Add Xen cross-build jobs .gitlab-ci.d/crossbuilds.yml | 78 ++++++++++++++++++++++++++---------- .gitlab-ci.yml | 5 +++ 2 files changed, 62 insertions(+), 21 deletions(-) -- 2.26.2
