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

Create a multi-arch buildpackage file instead of a buildpackage file for each target #2177

Open
ForestEckhardt opened this issue Jun 4, 2024 · 0 comments
Labels
status/ready Issue ready to be worked on. type/enhancement Issue that requests a new feature or improvement.
Milestone

Comments

@ForestEckhardt
Copy link
Contributor

Description

When creating a buildpackage file for a multi-arch buildpack multiple buildpackage files will be created one for each architecture that is supported by the buildpack.

Proposed solution

When creating a buildpackage file for a multi-arch buildpack to create a single buildpackage file in the same way that you can create a single multi-arch OCI image. This will mean that the artifact that is published and file that is created will behave identically allowing for the continued parity between the .cnb file and the images that are uploaded to the registry.

@ForestEckhardt ForestEckhardt added status/triage Issue or PR that requires contributor attention. type/enhancement Issue that requests a new feature or improvement. labels Jun 4, 2024
@jjbustamante jjbustamante added status/ready Issue ready to be worked on. and removed status/triage Issue or PR that requires contributor attention. labels Jun 4, 2024
@natalieparellano natalieparellano added this to the 0.36.0 milestone Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/ready Issue ready to be worked on. type/enhancement Issue that requests a new feature or improvement.
Projects
None yet
Development

No branches or pull requests

3 participants