jenkins is now producing ubuntu jammy builds for quincy branches, after the merge of https://github.com/ceph/ceph-build/pull/2206 is it possible to generate and sign jammy packages for our last quincy 17.2.7 point release?

On Fri, Feb 23, 2024 at 12:06 PM Casey Bodley <cbodley(a)redhat.com> wrote: > > On Thu, Feb 22, 2024 at 12:29 PM Casey Bodley <cbodley(a)redhat.com> wrote: > > > > there was a consensus to drop support for ubuntu focal and centos > > stream 8 with the squid release, and i'd love to remove those distros > > from the shaman build matrix for squid and main branches asap > > > > however, i see that quincy never supported ubuntu jammy, so our quincy > > upgrade tests still have to run against focal. that means we'd still > > have to build focal packages for squid > > > > would it be possible to start building jammy packages for quincy to > > allow those upgrade tests to run jammy instead? > > i'm not too familiar with ceph-build, but i think ceph-dev-new-trigger > is the right place to add this? > > https://github.com/ceph/ceph-build/pull/2206 > > > > > this isn't an issue on the centos side because we've been building > > centos 9 packages for quincy even though it's not listed in > > https://docs.ceph.com/en/latest/start/os-recommendations/#platforms

now that we have jammy builds for quincy, i've requested review/testing on https://github.com/ceph/ceph/pull/55976 to remove the last mentions of focal from our quincy upgrade suites on main i also prepared prs against ceph-build to stop building focal packages on main (https://github.com/ceph/ceph-build/pull/2220) and squid (https://github.com/ceph/ceph-build/pull/2221). those are blocked on the merge of https://github.com/ceph/ceph/pull/55976 and its squid backport

On Wed, Mar 27, 2024 at 10:31 AM Casey Bodley <cbodley(a)redhat.com> wrote: > > On Mon, Mar 25, 2024 at 11:33 AM Casey Bodley <cbodley(a)redhat.com> wrote: > > > > jenkins is now producing ubuntu jammy builds for quincy branches, > > after the merge of https://github.com/ceph/ceph-build/pull/2206 > > > > is it possible to generate and sign jammy packages for our last quincy > > 17.2.7 point release? > > (cc Josh and Yuri) > > i recall that we did something similar with debian bookworm packages > after the reef 18.2.1 release. who has the power/know-how to get this > done? we need this so ubuntu users have an upgrade path from quincy to > squid > > > > > On Fri, Feb 23, 2024 at 12:06 PM Casey Bodley <cbodley(a)redhat.com> wrote: > > > > > > On Thu, Feb 22, 2024 at 12:29 PM Casey Bodley <cbodley(a)redhat.com> wrote: > > > > > > > > there was a consensus to drop support for ubuntu focal and centos > > > > stream 8 with the squid release, and i'd love to remove those distros > > > > from the shaman build matrix for squid and main branches asap > > > > > > > > however, i see that quincy never supported ubuntu jammy, so our quincy > > > > upgrade tests still have to run against focal. that means we'd still > > > > have to build focal packages for squid > > > > > > > > would it be possible to start building jammy packages for quincy to > > > > allow those upgrade tests to run jammy instead? > > > > > > i'm not too familiar with ceph-build, but i think ceph-dev-new-trigger > > > is the right place to add this? > > > > > > https://github.com/ceph/ceph-build/pull/2206 > > > > > > > > > > > this isn't an issue on the centos side because we've been building > > > > centos 9 packages for quincy even though it's not listed in > > > > https://docs.ceph.com/en/latest/start/os-recommendations/#platforms