From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Stefano Stabellini" <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Doug Goldstein" <cardoe@cardoe.com>,
committers@xenproject.org
Subject: Re: [XEN PATCH v2 3/3] CI: New stage "containers" to rebuild some containers
Date: Wed, 20 Nov 2024 10:36:13 +0000 [thread overview]
Message-ID: <Zz27m452NC9gDlWo@l14> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2411191347100.1160299@ubuntu-linux-20-04-desktop>
On Tue, Nov 19, 2024 at 01:47:16PM -0800, Stefano Stabellini wrote:
> On Tue, 19 Nov 2024, Anthony PERARD wrote:
> > Rebuild rolling release containers when XEN_CI_REBUILD_CONTAINERS is
> > set. This is to be use with a scheduled pipeline.
> >
> > Signed-off-by: Anthony PERARD <anthony.perard@vates.tech>
>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Thanks!
I've scheduled a pipeline to run once a month so the Arch Linux and
Tumbleweed containers we'll get rebuilt regularly. Both container are
already up-to-date because I failed to use a different registry during
one of my test, but the build-jobs still works.
Cheers,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
prev parent reply other threads:[~2024-11-20 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 10:15 [XEN PATCH v2 0/3] CI: Allow automatic rebuild of rolling release containers Anthony PERARD
2024-11-19 10:15 ` [XEN PATCH v2 2/3] CI: Define XEN_REGISTRY variable Anthony PERARD
2024-11-19 10:15 ` [XEN PATCH v2 1/3] CI: Remove deprecated "only:variables" in favor of "rules:if" Anthony PERARD
2024-11-19 10:15 ` [XEN PATCH v2 3/3] CI: New stage "containers" to rebuild some containers Anthony PERARD
2024-11-19 21:47 ` Stefano Stabellini
2024-11-20 10:36 ` Anthony PERARD [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=Zz27m452NC9gDlWo@l14 \
--to=anthony.perard@vates.tech \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=committers@xenproject.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.