jib-core

Major Changes

• New method: JibContainerBuilder#describeContainer which returns new class: JibContainerDescription, containing a selection of information used for the Jib build.
• Each local base image layer is pushed immediately after being compressed, rather than waiting for all layers to finish compressing before starting to push.
• HTTP redirection URLs are no longer sanitized in order to work around an issue with certain registries that do not conform to HTTP standards. This resolves an issue with using Red Hat OpenShift and Quay registries.
• Containerizer.DEFAULT_BASE_CACHE_DIRECTORY has been changed on MacOS and Windows.
  • MacOS ($XDG_CACHE_HOME defined): from $XDG_CACHE_HOME/google-cloud-tools-java/jib/ to $XDG_CACHE_HOME/Google/Jib/
  • MacOS ($XDG_CACHE_HOME not defined): from $HOME/Library/Application Support/google-cloud-tools-java/jib/ to $HOME/Library/Caches/Google/Jib/
  • Windows ($XDG_CACHE_HOME defined): from $XDG_CACHE_HOME\google-cloud-tools-java\jib\ to $XDG_CACHE_HOME\Google\Jib\Cache\
  • Windows ($XDG_CACHE_HOME not defined): from %LOCALAPPDATA%\google-cloud-tools-java\jib\ to %LOCALAPPDATA%\Google\Jib\Cache\
• Containerizer#setAllowInsecureRegistries(boolean) and the sendCredentialsOverHttp system property are now effective for authentication service server connections.
• Fixed inefficient communications when interacting with insecure registries and servers (when Containerizer#setAllowInsecureRegistries(boolean) is set).
• Building a tarball with OCI format now builds a correctly formatted OCI archive.
• Now automatically refreshes Docker registry authentication tokens when expired, fixing the issue that long-running builds may fail with "401 unauthorized."

See CHANGELOG.md for more details.