Fix console output for internal Jib tasks/goals #3880
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
TadCordle
requested review from
balopat,
briandealwis,
chanseokoh,
dgageot,
loosebazooka,
nkubala and
tejal29
as code owners
Codecov Report
|
chanseokoh
approved these changes
Mar 26, 2020
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.
Fixes #3795.
Jib's internal tasks/goals (
_skaffoldFailIfJibOutOfDate,_jibSkaffoldInit,_jibFilesTaskV2,_jibSkaffoldSyncMap, and the maven equivalents) will now run with--console=plain(gradle) or--batch-mode(maven) to avoid unexpected output interfering with what we're trying to parse. For normal builds (jibDockerBuildandjibfor gradle,jib:dockerBuildandjib:buildfor maven), we continue passing the-Djib.console=plainflag as usual.@GoogleContainerTools/java-tools-build