New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails with Gradle Configuration Cache #3648
Comments
From the same documentation:
Most definitely not a bug, merely an enhancement, which would first require gradle changes as the core of dependencycheck is about reasoning about the dependencygraph. So while your request is valid and to be considered, it appears as if first gradle needs to improve on capabilities |
Sure, enhancement wasn't an option in the issue templates :) |
I've created a PR to disable configuration cache for the analyze task. This a new option provided by Gradle 7.4: by enabling it it won't be a blocker for people who want to take advantage of configuration cache. |
Still getting build failures on
|
in the mean time, can do this, but it is, of course, much slower: |
I'm still getting build failures with configuration cache enabled. Isn't it possible that the plugin opts-out? notCompatibleWithConfigurationCache () doesn't seem todo anything |
The Gradle task fails when Gradle Configuration Cache is enabled with this:
:app:dependencyCheckAnalyze
of typeorg.owasp.dependencycheck.gradle.tasks.Analyze
: cannot serialize object of type 'org.gradle.api.internal.project.DefaultProject', a subtype of 'org.gradle.api.Project', as these are not supported with the configuration cache.See https://docs.gradle.org/7.2/userguide/configuration_cache.html#config_cache:requirements:disallowed_types
:app:dependencyCheckAnalyze
of typeorg.owasp.dependencycheck.gradle.tasks.Analyze
: invocation of 'Task.project' at execution time is unsupported.See https://docs.gradle.org/7.2/userguide/configuration_cache.html#config_cache:requirements:use_project_during_execution
Gradle plugin 6.3.1
Steps to reproduce the behavior:
Expected behavior
It should run successfully with config cache enabled
The text was updated successfully, but these errors were encountered: