From: Anthony PERARD <anthony.perard@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [XEN PATCH 0/4] automation: Update containers to allow HTTPS access to xenbits
Date: Wed, 15 Feb 2023 12:02:04 +0000 [thread overview]
Message-ID: <20230215120208.35807-1-anthony.perard@citrix.com> (raw)
Patch series available in this git branch:
https://xenbits.xen.org/git-http/people/aperard/xen-unstable.git br.gitlab-containers-update-v1
There is work in progress [1] to update urls in our repo to use https, but
those https urls to xenbits don't work in our containers, due to an expired
root certificate. So we need to update those containers.
This series update the dockerfile where just rebuilding the container isn't enough.
I've tested the new containers but didn't updated them yet. You can see the
result in the following links (if you can access them). There are other
containers been test which didn't need dockerfile update.
https://gitlab.com/xen-project/people/anthonyper/xen/-/pipelines/777474218
https://gitlab.com/xen-project/people/anthonyper/xen/-/pipelines/778218868
Building randconfig on debian unstable seems to be an issue.
[1] https://lore.kernel.org/xen-devel/75d91def8234bceb41548147ee8af5fea52bd1d6.1675889602.git.demi@invisiblethingslab.com/
Cheers,
Anthony PERARD (4):
automation: Remove clang-8 from Debian unstable container
automation: Ignore package authentification issue in Jessie container
automation: Remove expired root certificates used to be used by let's
encrypt
automation: Add more aliases in containerize
automation/build/centos/7.2.dockerfile | 5 +++++
automation/build/centos/7.dockerfile | 5 +++++
automation/build/debian/jessie-i386.dockerfile | 7 +++++++
automation/build/debian/jessie.dockerfile | 7 +++++++
automation/build/debian/unstable-llvm-8.list | 3 ---
automation/build/debian/unstable.dockerfile | 12 ------------
automation/build/ubuntu/trusty.dockerfile | 5 +++++
automation/gitlab-ci/build.yaml | 10 ----------
automation/scripts/containerize | 3 +++
9 files changed, 32 insertions(+), 25 deletions(-)
delete mode 100644 automation/build/debian/unstable-llvm-8.list
--
Anthony PERARD
next reply other threads:[~2023-02-15 12:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 12:02 Anthony PERARD [this message]
2023-02-15 12:02 ` [XEN PATCH 1/4] automation: Remove clang-8 from Debian unstable container Anthony PERARD
2023-02-15 12:26 ` Andrew Cooper
2023-02-15 16:28 ` Anthony PERARD
2023-02-15 16:31 ` Andrew Cooper
2023-02-15 18:15 ` Andrew Cooper
2023-02-16 0:06 ` Stefano Stabellini
2023-02-15 12:02 ` [XEN PATCH 2/4] automation: Ignore package authentification issue in Jessie container Anthony PERARD
2023-02-15 12:36 ` Andrew Cooper
2023-02-15 16:21 ` Anthony PERARD
2023-02-15 12:02 ` [XEN PATCH 3/4] automation: Remove expired root certificates used to be used by let's encrypt Anthony PERARD
2023-02-15 12:41 ` Andrew Cooper
2023-02-16 0:14 ` Stefano Stabellini
2023-02-16 11:34 ` Anthony PERARD
2023-02-16 20:19 ` Stefano Stabellini
2023-02-15 12:02 ` [XEN PATCH 4/4] automation: Add more aliases in containerize Anthony PERARD
2023-02-15 12:29 ` Andrew Cooper
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=20230215120208.35807-1-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=cardoe@cardoe.com \
--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.