I want to use the R# command line tools (InspectCode) to check if devs introduced new issues to the codebase. I have setup a new build configuration in TeamCity using the "Inspections (Resharper)" and the scanning+reporting generally works.
But I have the problem that the scanning of our whole codebase simply takes too long for us. Our 259k LOC codebase takes 20-30mins to be fully scanned by the tools.
I would like to know how I can improve this situation. The TeamCity build step is using already caches by default but this seems not to help a lot. If I run multiple subsequent checks on the same codebase, it still takes more than 15mins to scan.
Has anybody experience on making this kind of checks faster?
The most reasonable thing for me is to simply scan only the files changed within the feature-branch. Existing issues on the develop branch are also a topic, but for the Pull-Request checking only the changes from the feature branch are relevant. I was hoping that the cache takes up this responsibility to only scan things that changed, but this seems not to be the case.
From a git-perspective it should be easily possible to create a list of files that were changed in the branch. But I cannot see how I could tell InspectCode to only re-scan those and report issues for them. There is only a general exclusion of paths and porjects possible via DotSettings, nothing to "only include" certain files.