Help community Gradle plugins adopt the configuration cache #13490
With the introduction of the Gradle configuration cache, community plugins may need to be adjusted. The goal of this issue is to track the status of community plugins.
For configuration cache support in core Gradle plugins see #13454
For more information about the configuration cache, how to use it and troubleshoot problems, please read the dedicated user manual chapter.
The following table displays the state of the support for the configuration cache in various community Gradle plugins. We started this list with the topmost downloaded plugins and added others we stumbled upon in the builds we tested. The list is not exhaustive, keep reading if you don't find your favorite plugin in the list.
We will be updating that list continuously.
If you find a plugin that you use in this list, please upvote the linked issues to make the plugin authors aware of your interest.
Reporting problems to community plugins
If you have tried the configuration cache on your build and found a problematic plugin, please report an issue to the plugin's bug tracker. The troubleshooting section of the dedicated user guide chapter explain how to reason about encountered problems.
A good way to report such problems to community plugin authors is by providing:
Here's a good example issue for a community plugin you can use as a template: michel-kraemer/gradle-download-task#156
Then please comment on this issue with a link to the plugin issue so we can add it to the list.
A plugin is missing in the list?
If you have tried the configuration cache on your build and found a problematic plugin that is not in the list above, please report an issue to the plugin's bug tracker as explained in the previous section and comment on this issue with a link to that issue so we can add it to the list.
If you are the author of a plugin that you want to make support the configuration cache or that already supports it, please comment on this issue so we can add it to the list.
The text was updated successfully, but these errors were encountered:
I have just added support for the configuration cache to the
Unless there's an okay API to allow us to have that, we'd like a way to tell Gradle to ignore configuration cache issues for our task, because it's just noise to our users and ourselves for something we can't address.
I'd like to report that