Support wildcard stack #331
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
test against bionic and jammy
fg-j
added
the
status/blocked
5 tasks
fg-j
added
semver:minor
ForestEckhardt
approved these changes
Jul 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Since this buildpack does not install any dependencies, I've set this to support the wildcard stack. Theoretically, any stack where the dotnet toolchain has been installed should be compatible with this buildpack.
I've added tests against the bionic and jammy builders. This requires a slight change to our integration script. See paketo-buildpacks/github-config#497
Use Cases
This facilitates us running the .NET Core buildpack on Jammy Jellyfish and other stacks in the future.
Checklist