From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v3] travis-ci: Disable C++ optional objects on AArch64 container
Date: Tue, 9 Feb 2021 14:23:37 +0000 [thread overview]
Message-ID: <20210209142337.GM1166421@redhat.com> (raw)
In-Reply-To: <21da6a3f-d2ce-91ff-6e9a-588af13c3369@redhat.com>
On Tue, Feb 09, 2021 at 03:16:46PM +0100, Thomas Huth wrote:
> On 09/02/2021 15.12, Philippe Mathieu-Daudé wrote:
> > On 2/9/21 2:41 PM, Peter Maydell wrote:
> > > On Tue, 9 Feb 2021 at 13:32, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> > > > Migration of this job is pending of Cleber's possibility to add an AArch64
> > > > runner to Gitlab-CI, right? Then we need someone to support and maintain
> > > > the hardware... I don't think anybody volunteered.
> > >
> > > We have the hardware already. Effectively Alex is maintaining it...
> >
> > I missed to read if Alex volunteered for this task but am certainly
> > happy if he is :) Although this should be documented somewhere (who
> > to contact if the AArch64 runner starts to fail?).
> >
> > Assuming Cleber's runner script is merged and working on the AArch64
> > runner, then we need to figure how contributors can use it.
> > Assuming this runner will be registered under the QEMU organization
> > namespace in Gitlab, then contributors would have to open a Merge
> > Request to trigger the CI jobs (similarly to when you push to the
> > /staging branch). Then we would cancel the MR. We can ask contributors
> > to cancel their MR once testing done.
>
> I'm not sure, but if I got that right, opening a MR will only trigger a CI
> run on side of the requester, not of the target project? For example, when I
> look at:
>
> https://gitlab.com/libvirt/libvirt/-/merge_requests/65
>
> the pipeline that is shown there ran on side of the requester, not on side
> of the libvirt project?
I'll have to search out the details, but there was an enhancement to
gitlab late last year that makes it possible for merge requests to
run CI in the context of the upstram project not the fork. It is
mentioned somewhere in the gitlab release notes.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-02-09 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 12:12 [PATCH v3] travis-ci: Disable C++ optional objects on AArch64 container Philippe Mathieu-Daudé
2021-02-09 12:53 ` Wainer dos Santos Moschetta
2021-02-09 13:29 ` Philippe Mathieu-Daudé
2021-02-09 13:41 ` Peter Maydell
2021-02-09 14:12 ` Philippe Mathieu-Daudé
2021-02-09 14:16 ` Thomas Huth
2021-02-09 14:23 ` Daniel P. Berrangé [this message]
2021-02-09 14:21 ` Daniel P. Berrangé
2021-02-09 18:09 ` Alex Bennée
2021-02-11 10:28 ` Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210209142337.GM1166421@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).