ceph-dev-new-trigger: start building quincy packages on jammy

[cbodley]

as described in https://lists.ceph.io/hyperkitty/list/dev@ceph.io/thread/ONAWOAE7MPMT7CP6KH7Y4NGWIP5SZ7XR/, lack of jammy packages for quincy is an obstacle to dropping ubuntu focal support on squid

[dmick]

I think this is likely sufficient

[cbodley]

thanks @dmick. we discussed this in the ceph leadership meeting today and agreed to add jammy for the next quincy point release

is there any risk to merging this as-is? it's possible that we'll hit new dependency issues with those jammy builds, but it shouldn't break anything else

[dmick]

I mean it'll make the overall build fail because one distroversion failed, so we should test after merge as much as we can

[cbodley]

I mean it'll make the overall build fail because one distroversion failed, so we should test after merge as much as we can

i just meant that one failure for jammy wouldn't prevent us from scheduling teuthology jobs against the existing supported distros

would you prefer to schedule a test build first? i will follow up on build failures either way

this just needs to be addressed before the next quincy point release and the squid release after. once we switch quincy->squid upgrade jobs to jammy, i'll raise another pr to remove focal builds on main/squid

[cbodley]

a friendly reminder that we'll need to release jammy packages for some quincy release before we can release squid

[cbodley]

i pushed a quincy branch and the jammy build was successful: https://shaman.ceph.com/builds/ceph/wip-quincy-jammy/