Replies: 2 comments 1 reply
-
Hello, In order to skip the Gradle step you can either disable the plugin by passing Considering the question about a cache key, @tiulpin, could you please help? |
Beta Was this translation helpful? Give feedback.
-
@brichbash - I now had a situation where no cache was found, and then the Qodana action printed
So I believe this is the answer why the cache is ever-increasing when I change dependencies. I applied the setting for the property, and it works well. I looked into the docs and found this also documented. The documentation also indicates that I can have multiple plugins disabled using a comma ( So (with a comma)
ends up as (with a blank)
Is there a workaround for this? |
Beta Was this translation helpful? Give feedback.
-
For one of my projects I want to check the docs in the project using the Grazie and the AsciiDoc plugin. For that, I wouldn't need the Gradle parts of the project initialized when running Qodana: https://github.com/asciidoctor/asciidoctor-intellij-plugin/
Due to the initialization of Gradle, it downloads (unnecessarily) ~3,3 GB of data that it doesn't need. In addition, I keep wondering what Qodana uses as a cache key, that is: what change to wich file invalidates the cache -- see https://github.com/asciidoctor/asciidoctor-intellij-plugin/actions/runs/3268249646/jobs/5374431345 for a previous run.
Previously I ran Qodana only on the docs folder, but with the changes to inspect the latest Git commits this has proven no longer viable.
So I wonder: Can I teach Qodana not to initialize Gradle?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions