Re: [PATCH v4 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI)

2021-02-04 Thread Thomas Huth
On 03/02/2021 22.06, Cleber Rosa wrote: On Thu, Jan 28, 2021 at 12:51:20PM +0100, Thomas Huth wrote: [...] Could you elaborate on what's left to do to get the s390x and aarch64 runners enabled, and rebase your patches if necessary Basically what's needed is to enable the jobs, meaning committ

Re: [PATCH v4 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI)

2021-02-03 Thread Cleber Rosa
On Thu, Jan 28, 2021 at 12:51:20PM +0100, Thomas Huth wrote: > On 19/10/2020 03.49, Cleber Rosa wrote: > > 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. Simple usage looks like: > > > >

Re: [PATCH v4 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI)

2021-01-28 Thread Thomas Huth
On 19/10/2020 03.49, Cleber Rosa wrote: 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. Simple usage looks like: git push remote staging ./scripts/ci/gitlab-pipeline-status --verbose --