Chanseok Oh
Chanseok Oh
`USE_CURRENT_TIMESTAMP` is not supported for `filesModificationTime`. If this were supported, would you still need the option to preserve the filesystem timestamps? However, this is extremely bad, since you lose entire...
Thanks for the feedback, @hugolumsdon. > (even if it's just ${maven.build.timestamp}) I strongly discourage using a build-time timestamp, since this loses the entire cache benefit. For example, if the size...
> I think your answer is less about 'best practice' and more about the JIB caching implementation Just wanted to quickly point out that the image caching is universal and...
No worries for more input. Happy to discuss. We'd like to understand users' use cases and better support them. > However if you honoured the WAR timestamps and the same...
Thanks! The Jib layering is like an implementation detail and not documented. This is mostly intended, and I'll explain why. People who are versed in Docker know what they are...
Hi @bsideup, Thanks for the feedback. I believe you are talking about turning the `DockerClient` `class` into a Java `interface`, right? Technically it's easy to turn it into an `interface`,...
> so that Jib can be used on systems where Docker CLI is not available, or fine tune the client (e.g. point it to a remove Docker daemon over some...
Oh, for `jib-core`, you can set the variables via `DockerDaemonImage.setDockerEnvironment()`.
Ref: https://github.com/GoogleContainerTools/jib/issues/3571#issuecomment-1037107437