[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Cleber Rosa
Subject: Re: [PATCH v4 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI)
Date: Wed, 3 Feb 2021 16:06:03 -0500

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:
> > 
> >     git push remote staging
> >     ./scripts/ci/gitlab-pipeline-status --verbose --wait
>  Hi Cleber,
> since the QEMU project is now using the gitlab repo as main repository, it
> should now be possible to finally enable these custom runners, too, I think.

I couldn't agree more!

> 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 committing the
relevant snippets to the "gitlab-ci.{yml,d/*}" files.

Both ansible playbooks have been run on both machines, so the gitlab-runner
and tooling to build QEMU are in place.  The gitlab-runners have also
been registered on the "qemu-project/qemu" GitLab repo.

I'll send a rebased/updated version of the playbooks, gitlab-ci.yml
configurations, etc.  In it, I'll propose that we enable the jobs, but
ignore errors for now (allow_failure: true), because it'll ease the
review.  Once the jobs prove mature, waiving of failures can be

How does that sound?

- Cleber.

>  Thanks,
>   Thomas

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]