Google Java container technology, Jib has become a huge favorite for developers as it can turn just about any Java app into an optimized container image, and allowing developers to fully optimize the creation of Docker containers.
While Jib helps to build container images in a declarative manner, which delivers an impressively short edit-compile-test development cycle, and transparently applies container best practices, that doesn’t require the installation of Docker or writing a script-like Dockerfiles.
Now, Google has extended the containerization technology with the Jib Plugin Extension Framework, thus enabling customization of the Jib plug-ins for both the Maven and Gradle build systems.
About the Jib Plugin Extension Framework
Jib Plugin Extension Framework is meant to allow developers to easily extend and tailor Jib to perform their custom-specific tasks. And they can use the extension and apply it to any project, for instance, if a developer wants to add custom image layers whose contents come from a ZIP file, an extension can be created for it.
It allows you to tweak every aspect of the image you want to build, powered by Container Build Plan Specification, which is a general, tool-agnostic process of describing how to build an image.
The extension framework actually opens up a lot of possibilities for developers, from fine-tuning images to containerizing GraalVM native images or jlink images for small footprint.
How Jib sets a new course for Java containers
Jib made debut in June, and it became generally available, it has cornered a sizable community around it, with the core Jib team haven been working on expanding the ecosystem.
Google has also improved application framework support for Jib, with the recently released Maven and Gradle Jib extensions for Spring Boot, Quarkus and a Maven extension for GraalVM. And the Jib Extensions repository on GitHub is perhaps where you can discover great extensions for your builds, or perhaps, join the core Jib team in creating more useful extensions.