Switch tests from heroku/buildpacks:20
to heroku/builder:20
#117
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.
Since the
heroku/buildpacks:20
image is about to be deprecated, and has been replaced by the newly addedheroku/builder:20
for those that need to use a Heroku-20 based builder.The build and run images used by
heroku/builder:20
are the same as those used byheroku/buildpacks:20
- the only differences between the builders are the included buildpacks (which is somewhat irrelevant for these integration tests, since the buildpack under test will be injected instead).The smoke tests in the
heroku/builder
GitHub repo are still testing against all image variants (until such time as we make the legacy images error with an EOL message), so we still have test coverage against them.See:
heroku/cnb-builder-images#394
https://salesforce.quip.com/0JtbAYiWZYk6
GUS-W-14186015.