Adopt Ubuntu Noble

[loewenstein-sap]

While the RFC about Ubuntu LTS adoption is still in motion for the part about in general adopting every LTS, this is an issue to track work on immediate adoption of Ubuntu 24.04 (aka Noble Numbat).

• Provide Noble based stacks
  @paketo-buildpacks/stacks-maintainers could you please check the following repositories. We need to make sure that they receive updates and are part of the regular release work. Also, we might want to bump them to 0.1.0 now and latest when we are entirely finished with adopting Noble we should have a 1.0.0 release.
  cc @paketo-buildpacks/stacks-contributors
  • https://github.com/paketo-buildpacks/noble-static-stack
  • https://github.com/paketo-buildpacks/noble-tiny-stack
  • https://github.com/paketo-buildpacks/noble-base-stack
  • https://github.com/paketo-buildpacks/noble-full-stack
• Provide Noble based buildpackless builders
  @paketo-buildpacks/builders-maintainers could you please check the following repositories. For now, I think only the buildpackless-base repo is actually prepared already, the rest needs to be filled. We also need to make sure the repos are setup for automatic updates and releases. And we should go to 0.1.0 and 1.0.0 over the course of implementation.
  cc @paketo-buildpacks/builders-contributors
  • https://github.com/paketo-buildpacks/builder-noble-buildpackless-static
  • https://github.com/paketo-buildpacks/builder-noble-buildpackless-tiny
  • https://github.com/paketo-buildpacks/builder-noble-buildpackless-base
  • https://github.com/paketo-buildpacks/builder-noble-buildpackless-full
• Validate buildpacks are working with Noble
  All buildpacks need to be evaluated on a buildpackless builder and then added to the buildpackfull builders' order.toml.
  • @paketo-buildpacks/java-maintainers
  • @paketo-buildpacks/nodejs-maintainers
  • @paketo-buildpacks/dotnet-core-maintainers
  • @paketo-buildpacks/go-maintainers
  • @paketo-buildpacks/web-servers-maintainers
  • @paketo-buildpacks/python-maintainers
  • @paketo-buildpacks/php-maintainers
  • @paketo-buildpacks/ruby-maintainers
• Provide Noble based standard builders (i.e. including the usual buildpacks)
  • @paketo-buildpacks/steering-committee we need to create the repositories
  • @paketo-buildpacks/builders-maintainers once the repositories exist, they need to be filled

[pacostas]

The core functionality for the noble-*-stack is not synced with the github-config. This is visible from the files that are included on the .github/.syncignore

• workflows/create-release.yml
• workflows/test-pull-request.yml
• workflows/push-image.yml

and on the scripts/.syncignore

• receipts.sh
• .util/tools.json
• .util/tools.sh

Based on that I've opened a PR that syncs all the configuration from the github-config and also supports multi-arch for all the types of stacks paketo-buildpacks/noble-base-stack#10 .

This implementation is based on the noble-base-stack current implementation with a few parts taken from jammy-tiny-stack. Also is something we have tested on the majority of the stacks and we have been using it on ubi-base-stack for the past few months. I would say that is stable enough to use across all the stacks.

[pacostas]

The builders do not have a release yet, I think it would be nice to have a release first, as this would ensure that everyone tests against the same builder and also not having each team to do the effort of creating/pushing a builder locally to test against.