[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v5 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI)
From: |
Alex Bennée |
Subject: |
Re: [PATCH v5 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI) |
Date: |
Fri, 21 May 2021 11:29:23 +0100 |
User-agent: |
mu4e 1.5.13; emacs 28.0.50 |
Cleber Rosa <crosa@redhat.com> writes:
> TL;DR: this should allow the QEMU maintainer to push to the staging
> branch, and have custom jobs running on the project's aarch64 and
> s390x machines. Jobs in this version are allowed to fail, to allow
> for the inclusion of the novel machines/jobs without CI disruption.
> Simple usage looks like:
>
> git push remote staging
> ./scripts/ci/gitlab-pipeline-status --verbose --wait
>
> Long version:
>
> The idea about a public facing Gating CI for QEMU was summarized in an
> RFC[1]. Since then, it was decided that a simpler version should be
> attempted first.
>
> At this point, there are two specific runners (an aarch64 and an s390x)
> registered with GitLab, at https://gitlab.com/qemu-project, currently
> setup to the "qemu" repository.
>
> Changes from v4:
Was there a v6 I missed?
--
Alex Bennée
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [PATCH v5 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI),
Alex Bennée <=