GoogleContainerTools
FYI: Created a new idiomatic gradle plugin around jib-core
As discussed in a few issues, I've been kicking around ways to solve for some of the constraints i've bumped into using Jib and the OOTB jib gradle plugin, and I ended up rolling them up into a separate gradle plugin that I thought others might find useful.
Plugin here, early days not published to gradle plugin portal yet but the bones are there: https://github.com/bsycorp/gradle-jib-plugin
The intent of the project is to create an idiomatic Gradle plugin around jib-core that follows all the Gradle best practices for the best Gradle experience (build cache, configuration caching, up-to-date checking, Property<> usage, locking concurrent base image pulls etc). I know the Jib project has to solve for both Gradle and Maven (probably others?) and that means its hard or impossible to achieve these Gradle specific things, so I just solved for Gradle =).
If you spot anything that could be improved with the jib-core integration or anything in general, happy to hear 👍
This looks very interesting, @nhoughto . I may be able to give your plugin a try for building containers with Micronaut!
Alternative implementations strengthen the ecosystem. If you prefer to use more of the existing plugin's functionality, you may be interested in creating a Jib Gradle plugin extension (https://github.com/GoogleContainerTools/jib-extensions).
The way this was built and the overall intent (idiomatic gradle) means that an extension wasn’t going to work, not enough control. I did try that first tho! =) On 1 Apr 2022, 1:30 AM +1100, Elena Felder @.***>, wrote:
Alternative implementations strengthen the ecosystem. If you prefer to use more of the existing plugin's functionality, you may be interested in creating a Jib Gradle plugin extension (https://github.com/GoogleContainerTools/jib-extensions). — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>