| Message ID | 20240703142002.1662874-1-andrew.cooper3@citrix.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | CI: Fixes, part 1 | expand |
On Wed, 2024-07-03 at 15:19 +0100, Andrew Cooper wrote: > Minimum fixes to rebuild the containers, following the HEREDOC > problems. > > Unrelated to the HEREDOC problems, Archlinux and CentOS 7 need > aditional > chagnes to rebuild. > > There will be subsequent work to make some improvements to CI for > 4.19, so in > particular we're testing with up-to-date LTS distros. If we really want to test with up-to-date LTS distros in 4.19 then it probably make sense to postpone release date to July 29 to be sure that everything is okay. July 29 is still fit in our 2 times release cycle per year. ~ Oleksii > > Andrew Cooper (4): > CI: Formalise the use of heredocs > CI: Adjust the usage of inline files > CI: Drop bin86/dev86 from archlinux container > CI: Rework the CentOS7 container > > automation/build/README.md | 10 ++- > .../build/alpine/3.18-arm64v8.dockerfile | 1 + > automation/build/alpine/3.18.dockerfile | 1 + > .../archlinux/current-riscv64.dockerfile | 1 + > automation/build/archlinux/current.dockerfile | 3 +- > automation/build/centos/7.dockerfile | 71 ++++++++++------- > -- > .../bookworm-arm64v8-arm32-gcc.dockerfile | 1 + > .../build/debian/bookworm-arm64v8.dockerfile | 1 + > .../build/debian/bookworm-cppcheck.dockerfile | 1 + > .../build/debian/bookworm-i386.dockerfile | 1 + > automation/build/debian/bookworm.dockerfile | 1 + > .../build/debian/bullseye-ppc64le.dockerfile | 1 + > .../build/debian/buster-gcc-ibt.dockerfile | 1 + > .../build/debian/jessie-i386.dockerfile | 3 +- > automation/build/debian/jessie.dockerfile | 3 +- > .../build/debian/stretch-i386.dockerfile | 3 +- > automation/build/debian/stretch.dockerfile | 3 +- > automation/build/fedora/29.dockerfile | 1 + > .../build/suse/opensuse-leap.dockerfile | 1 + > .../build/suse/opensuse-tumbleweed.dockerfile | 1 + > automation/build/ubuntu/bionic.dockerfile | 1 + > automation/build/ubuntu/focal.dockerfile | 1 + > automation/build/ubuntu/trusty.dockerfile | 1 + > .../build/ubuntu/xenial-xilinx.dockerfile | 1 + > automation/build/ubuntu/xenial.dockerfile | 1 + > automation/build/yocto/yocto.dockerfile.in | 2 + > .../alpine/3.18-arm64v8.dockerfile | 1 + > .../tests-artifacts/alpine/3.18.dockerfile | 1 + > .../kernel/5.19-arm64v8.dockerfile | 1 + > .../tests-artifacts/kernel/6.1.19.dockerfile | 1 + > .../6.0.0-arm64v8.dockerfile | 1 + > .../qemu-system-ppc64/8.1.0-ppc64.dockerfile | 1 + > 32 files changed, 82 insertions(+), 40 deletions(-) > > > base-commit: fb76e08a8f7a61dfbc07d0f335f1623bca650d7f
On 04/07/2024 11:37 am, Oleksii wrote: > On Wed, 2024-07-03 at 15:19 +0100, Andrew Cooper wrote: >> Minimum fixes to rebuild the containers, following the HEREDOC >> problems. >> >> Unrelated to the HEREDOC problems, Archlinux and CentOS 7 need >> aditional >> chagnes to rebuild. >> >> There will be subsequent work to make some improvements to CI for >> 4.19, so in >> particular we're testing with up-to-date LTS distros. > If we really want to test with up-to-date LTS distros in 4.19 then it > probably make sense to postpone release date to July 29 to be sure that > everything is okay. July 29 is still fit in our 2 times release cycle > per year. Testing with up-to-date distros is trivial, when I can rebuild the containers. I've already got "CI: Fixes, part 2" and "part 3" in progress, hoping to post today, all for 4.19. What matters, specifically for 4.19 at this point, is that we put in place testing such that {staging,stable}-4.19 branches are tested suitably after release. It would be really embarrassing for the Xen 4.19 release if it didn't work with e.g. Ubuntu Noble. ~Andrew
On Thu, 2024-07-04 at 11:51 +0100, Andrew Cooper wrote: > On 04/07/2024 11:37 am, Oleksii wrote: > > On Wed, 2024-07-03 at 15:19 +0100, Andrew Cooper wrote: > > > Minimum fixes to rebuild the containers, following the HEREDOC > > > problems. > > > > > > Unrelated to the HEREDOC problems, Archlinux and CentOS 7 need > > > aditional > > > chagnes to rebuild. > > > > > > There will be subsequent work to make some improvements to CI for > > > 4.19, so in > > > particular we're testing with up-to-date LTS distros. > > If we really want to test with up-to-date LTS distros in 4.19 then > > it > > probably make sense to postpone release date to July 29 to be sure > > that > > everything is okay. July 29 is still fit in our 2 times release > > cycle > > per year. > > Testing with up-to-date distros is trivial, when I can rebuild the > containers. > > I've already got "CI: Fixes, part 2" and "part 3" in progress, hoping > to > post today, all for 4.19. > > What matters, specifically for 4.19 at this point, is that we put in > place testing such that {staging,stable}-4.19 branches are tested > suitably after release. > > It would be really embarrassing for the Xen 4.19 release if it didn't > work with e.g. Ubuntu Noble. Agree, it makes sense. Release-Acked-by: Oleksii Kurochko <oleksii.kurochko@gmail.com> ~ Oleksii