Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Paketo Stacks RFC 0004: Jammy Jellyfish #1

Closed
3 tasks done
Tracked by #133
fg-j opened this issue May 10, 2022 · 3 comments
Closed
3 tasks done
Tracked by #133

Implement Paketo Stacks RFC 0004: Jammy Jellyfish #1

fg-j opened this issue May 10, 2022 · 3 comments
Assignees

Comments

@fg-j
Copy link

fg-j commented May 10, 2022

Paketo Stacks RFC 0004 states that Paketo should support a "full" stack on top of Ubuntu Jammy Jellyfish. To implement this RFC:

  • Determine which OS packages should be installed on the Full Jammy stack. These may be identical to those installed on the bionic Full stack. (See the bionic Full repo)
  • Create a stack descriptor file for this stack and check it into this repo. The descriptor should have the following attributes:
    • stack id: io.buildpacks.stacks.jammy
    • the UID for build and run phases should differ (but be in the same group)
  • Set up automation on this repo that builds the stack using jam create-stack and publishes the stack to the appropriate tags:
    • paketobuildpacks/build-jammy-full:latest
    • paketobuildpacks/build-jammy-full:1.2.3
    • paketobuildpacks/run-jammy-full:latest
    • paketobuildpacks/run-jammy-full:1.2.3
@sophiewigmore
Copy link
Member

@fg-j as a heads up, I wouldn't lean too heavily on the testing workflows from the Stacks repo. The test-create-stack workflow specifically has issues running from forks. I'd love to see these workflows reworked a little bit if possible while we're adding new stacks.

@fg-j fg-j added the status/blocked This issue has been triaged and resolving it is blocked on some other issue label May 23, 2022
@fg-j
Copy link
Author

fg-j commented May 23, 2022

We'd like to make more progress on paketo-buildpacks/jammy-tiny-stack#1 before picking this up – the precedent set by Tiny can be followed here.

@fg-j fg-j removed the status/blocked This issue has been triaged and resolving it is blocked on some other issue label Jun 21, 2022
@fg-j fg-j moved this from ❓Not scoped to 📝 Todo in Paketo Workstreams Jun 21, 2022
@robdimsdale robdimsdale moved this from 📝 Todo to 🚧 In Progress in Paketo Workstreams Jun 22, 2022
@robdimsdale robdimsdale self-assigned this Jun 22, 2022
@robdimsdale
Copy link
Member

With the release of v0.0.3 we can call this initial implementation complete. Closing.

Repository owner moved this from 🚧 In Progress to ✅ Done in Paketo Workstreams Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants