Add go_buildpack to the list of buildpacks used for tests #692
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
arjun024
added a commit
to cloudfoundry/ruby-buildpack
that referenced
this pull request
Sep 4, 2024
arjun024
added a commit
to cloudfoundry/ruby-buildpack
that referenced
this pull request
Sep 4, 2024
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.
Context
With the removal of cflinuxfs3 buildpacks from Shepherd environments, tests using another Buildpack (Dynatrace, proxy) do not work for cflinuxfs3. With this change, the Go Buildpack is downloaded and added to the list of buildpacks before running the tests.
This is only necessary for Buildpacks that use
Switchbladeand require a second buildpack for testing. All other buildpacks that use Cutlass support it natively by adding the URL in the Buildpack list (As done previously with Staticfile, PHP, and Dotnet).