qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Laurent Vivier" <laurent@vivier.eu>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PULL 0/3] Fixes 20200825 patches
Date: Fri, 28 Aug 2020 17:40:04 +0100	[thread overview]
Message-ID: <20200828164004.GR224144@redhat.com> (raw)
In-Reply-To: <CAFEAcA8i35pGHquuoT1Cmrk7QZrvV0SmQt-oy1N-3pQjD=ou9A@mail.gmail.com>

On Fri, Aug 28, 2020 at 05:29:44PM +0100, Peter Maydell wrote:
> On Fri, 28 Aug 2020 at 06:13, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > On Thu, Aug 27, 2020 at 11:23:58AM +0100, Peter Maydell wrote:
> > >
> > > Also we need figure out how to handle the conflict between
> > > "gitlab's git repo is mirrored (by perodic push?) from
> > > git.qemu.org" and "test by pushing to the gitlab staging
> > > branch", because the former overwrites the changes that
> > > the latter makes.
> >
> > Pushing to a qemu fork runs CI too, so the staging branch doesn't have
> > to live in the official qemu-project repo.
> 
> We aren't going to let the project's gitlab runners (the aarch64,
> s390x, etc systems) run just anybody's CI jobs, because they're
> a very limited resource: they will only run for things pushed
> to the official repo.

Runners are registered to the project, so we could create a separate
gitlab.com/qemu-project/qemu-staging  repo just for purpose of CI
and that would have access to the runners.

I don't know how the mirroring is setup currently, but if we use
GitLab's own pull based mirroring, you can configure it to only
mirror protected branches.  We could thus mark "master" and any
stable branches as protected.  GitLab should then mirror those,
without overwriting any other branches you have. So that ought
to let you create a staging branch in the main repo.


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 :|



      reply	other threads:[~2020-08-28 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25  6:20 [PULL 0/3] Fixes 20200825 patches Gerd Hoffmann
2020-08-25  6:20 ` [PULL 1/3] meson: drop keymaps symlink Gerd Hoffmann
2020-08-25  6:20 ` [PULL 2/3] meson: move xkbcommon to meson Gerd Hoffmann
2020-08-25  6:20 ` [PULL 3/3] meson: avoid compiling qemu-keymap by default Gerd Hoffmann
2020-08-25 12:59 ` [PULL 0/3] Fixes 20200825 patches Peter Maydell
2020-08-27  7:20 ` Thomas Huth
2020-08-27  9:28   ` Gerd Hoffmann
2020-08-27 10:23   ` Peter Maydell
2020-08-28  5:13     ` Gerd Hoffmann
2020-08-28 16:29       ` Peter Maydell
2020-08-28 16:40         ` Daniel P. Berrangé [this message]

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=20200828164004.GR224144@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@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).