Conversation
This allows to use the buildpack with the newer lifecycle images. Currently the supported heroku builder (heroku/builder:22) uses the lifecycle version >18, and that one only supports buildpacks API >= 0.7 See https://github.com/buildpacks/lifecycle for details. * Moved bin/compile -> bin/build * Using the CNB environment variables instead of arguments for the scripts * Added buildpack.toml and package.toml to meet the buildpack 0.10 spec. * Removed the bin directory from the gitignore. Signed-off-by: David Caro <david@greyllama.cc>
1776584 to
e7d9ef8
Compare
|
Hello @david-caro Thank you for you contribution💪 I've reviewed the changes. As I can see there are the breaking change for Heroku buildpack. The |
|
Oh! I think this is not directly needed actually, it seems heroku provides a "cloud native"-ified version of each buildpack at the url: https://buildpack-registry.heroku.com/cnb/jincod/dotnetcore (note the And it even fixes the return code for the detect script and such: So the solution there seems to be to pull the buildpack from that url instead of using the code from the repository (or the releases page). Let me try see if that solves it on my side, but there might not be any changes required :) |
|
Unfortunately does not work either xd Note that you can't use the |
Signed-off-by: David Caro <dcaro@wikimedia.org>
|
I added the link from build to compile, can you try it out @jincod? |
|
Hi @david-caro, Thank you for the update. I will run some tests. BTW Have you checked this project https://github.com/paketo-buildpacks/dotnet-core? |
This allows to use the buildpack with the newer lifecycle images.
Currently the supported heroku builder (heroku/builder:22) uses the lifecycle version >18, and that one only supports buildpacks API >= 0.7
See https://github.com/buildpacks/lifecycle for details.