we have the problem that our Maven scanner always writes: “Server-side caching is enabled. The Java analyzer was able to leverage cached data from previous analyses for 0 out of 9 files. These files will not be parsed.”
The table in the database also seems to be relatively small. Could it be that something is not working here?
Our scan takes about 20 minutes, which is really extreme considering that even for small changes everything gets scanned again. How can this be optimized, or how can the cache be activated?
You see log lines about the cache when you’re doing a branch analysis because the cache is updated from the most recent branch analysis so that it will be available to the PR anlaysis.
Can you provide a PR analysis log?
The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.
Hey,
thanks for the quick response.
We don’t perform branch analysis on feature branches, only on PRs. We only perform branch analysis on the master branch.
I’ll check right away whether I can provide a log excerpt. Since this is an internal server, I’m not sure how much of the log I’m allowed to share.
Hey,
while fetching the logs for sharing, I noticed that the cache actually does a good job during PR validation. So the problem was probably sitting in front of the screen (me).
That basically makes the issue obsolete.
Many, many thanks ^^
