Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Maven --batch-mode not supressing jib progress report

See original GitHub issue

When captured by non-interactive terminal, Jib’s maven plugin output of transfer progress makes job logs much longer / dirtier than they should be. This is a minor, but very real pain point when trying to keep Continuous Integration logs meaningful and readable.

Maven provides the --batch-mode CLI option to suppress such progress reports. Jib should use the same mechanism to suppress it’s output when specified.

Here’s a partial sample output of jib when running in non-interactive terminal:

...
[INFO] Executing tasks:
[INFO] [==================            ] 60.7% complete
[INFO] > building dependencies layer
[INFO] > setting up to push layers
[INFO] > setting up to push layers
[INFO] > pulling base image layer sha256:6ac6f91f019c1...
[INFO] 
[INFO] Executing tasks:
[INFO] [==================            ] 60.8% complete
[INFO] > building dependencies layer
[INFO] > setting up to push layers
[INFO] > setting up to push layers
[INFO] > pulling base image layer sha256:6ac6f91f019c1...
[INFO] 
[INFO] Executing tasks:
[INFO] [==================            ] 60.9% complete
[INFO] > building dependencies layer
[INFO] > setting up to push layers
[INFO] > setting up to push layers
[INFO] > pulling base image layer sha256:6ac6f91f019c1...
[INFO] 
[INFO] Executing tasks:
[INFO] [==================            ] 61.0% complete
...