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.

Sign up for GitHub

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

Jump to bottom

Support buildpacks with the wildcard stack #741

Closed
matthewmcnew opened this issue Jun 22, 2021 · 3 comments
Closed

Support buildpacks with the wildcard stack #741

matthewmcnew opened this issue Jun 22, 2021 · 3 comments
Assignees
@tomkennedy513
Labels
0.4.0 enhancement New feature or request

Comments

@matthewmcnew
Copy link
Collaborator

matthewmcnew commented Jun 22, 2021 •
edited
Loading

Currently, buildpacks with a wildcard stack will not be properly recognized by kpack.

RFC: buildpacks/rfcs#97
@matthewmcnew matthewmcnew added enhancement New feature or request 0.4.0 labels Jun 28, 2021
@tomkennedy513 tomkennedy513 self-assigned this Jul 16, 2021
@mgibson1121
Copy link
Contributor

mgibson1121 commented Jul 22, 2021 •
edited
Loading

Is there an easy way to validate this?

@matthewmcnew matthewmcnew mentioned this issue Jul 22, 2021
Merged
@matthewmcnew
Copy link
Collaborator Author

This can be validated with any of the heroku jvm buildpacks: https://github.com/heroku/buildpacks-jvm/releases.

@matthewmcnew
Copy link
Collaborator Author

You can also package a simple buildpack locally with the wildcard stack with pack buildpack new & edit buildpack.toml & pack buildpack package

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tomkennedy513 tomkennedy513

Labels
0.4.0 enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@matthewmcnew @tomkennedy513 @mgibson1121