Re: non-x86 runners in the Gitlab-CI (was: Re: [PATCH 12/12] configure: bump min required CLang to 7.0.0 / XCode 10.2)

[Philippe Mathieu-Daudé]

Hi Daniel,

On Wed, May 12, 2021 at 4:00 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
> On Wed, May 12, 2021 at 03:55:59PM +0200, Thomas Huth wrote:
> > On 12/05/2021 15.47, Willian Rampazzo wrote:

> > > I don't know if you saw this:
> > > https://docs.travis-ci.com/user/billing-overview/#partner-queue-solution.
> > >
> > > tl;dr, Travis now has support from partners to run non-x86 arch. It is
> > > always good to have a plan B, like qemu own CI runners, but, at least,
> > > with these non-x86 arch available on Travis, we will have some time to
> > > breathe.

>   "The build job under Partner Queue Solution costs 0 credits per
>    started minute. At the moment of introducing Partner Queue Solution
>    active accounts on the Usage based Plans, including the Free Plan,
>    with a balance of zero or fewer credits, balance is updated to
>    hold 1 credit. Thus everybody can use Partner Queues without
>    requesting Travis CI support to grant additional credits. If you
>    run into a negative account balance after that, you still need to
>    file an additional request."
>
> IOW, anyone ought to be able to use non-x86 jobs, bt if you accidentally
> run an x86 job and get into 0 (or negative) credits, then you won't even
> be able to use non-x86 jobs.

You once showed a script on GitLab triggering Travis-CI jobs and reporting
the success/failure on GitLab (or was it Cirrus-CI?). Is it possible to use
something similar with QEMU to integrate Travis-CI jobs with GitLab
pipeline?