From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH-for-6.0.1 0/2] gitlab-ci: Only push docker images to mainstream registry from /master
Date: Wed, 27 Oct 2021 11:24:57 +0100 [thread overview]
Message-ID: <YXko+T1rsVqtSZ5g@redhat.com> (raw)
In-Reply-To: <6a9cfd05-e2fd-0091-44c8-25f7229d5877@redhat.com>
On Wed, Oct 27, 2021 at 12:09:39PM +0200, Philippe Mathieu-Daudé wrote:
> +Richard/Peter
>
> On 10/27/21 10:49, Daniel P. Berrangé wrote:
> > On Wed, Oct 27, 2021 at 07:26:54AM +0200, Philippe Mathieu-Daudé wrote:
> >> Hi Michael,
> >>
> >> 2 more patches to avoid gitlab-ci mayhem when you push the
> >> stable tags. See this cover for more info:
> >> https://www.mail-archive.com/qemu-devel@nongnu.org/msg846861.html
> >
> > Please don't push this to stable - Thomas points out that it is broken
> > when any changes to dockerfiles are made.
>
> But we still don't want to update the registry with these old
> images...
>
> What is the plan then, hold the stable tag until we figure out
> the best fix?
>
> Otherwise Michael can use 'git-push --push-option=ci.skip' to
> not trigger a CI pipeline when pushing stable tags (running
> CI pipelines previously in his own gitlab namespace).
Yes, I'd suggest that approach currently, until we figure out a
real long term solution.
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-10-27 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 5:26 [PATCH-for-6.0.1 0/2] gitlab-ci: Only push docker images to mainstream registry from /master Philippe Mathieu-Daudé
2021-10-27 5:26 ` [PATCH-for-6.0.1 1/2] gitlab: only let pages be published from default branch Philippe Mathieu-Daudé
2021-10-27 5:26 ` [PATCH-for-6.0.1 2/2] gitlab-ci: Only push docker images to registry from /master branch Philippe Mathieu-Daudé
2021-10-27 8:49 ` [PATCH-for-6.0.1 0/2] gitlab-ci: Only push docker images to mainstream registry from /master Daniel P. Berrangé
2021-10-27 10:09 ` Philippe Mathieu-Daudé
2021-10-27 10:24 ` Daniel P. Berrangé [this message]
2021-10-27 14:33 ` Michael Roth via
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=YXko+T1rsVqtSZ5g@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=michael.roth@amd.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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).