This repository has been archived by the owner on Oct 27, 2022. It is now read-only.
fix default build mechanism priority for jib (address #7) #28
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.
This PR addresses issue #7 in part.
For all Java-based samples (
pom.xml
in the sample's root directory), we're going to use Jib, regardless of whether or not the sample also has aDockerfile
included in its root directory.If we want, we can also include a
—no-jib
flag here that would force the program to usegcloud builds submit
for all samples.