Hi @santhonisz,
in general you shouldn’t care too much about cache invalidation as it is implementation detail and it could change in the future. In any case this is a list of things (more or less exhaustive) invalidating the cache:
- Upgrade/Downgrade of SonarQube version if it comes with different version of SonarCFamily plugin
- Upgrade/Downgrade of SonarCFamily plugin
- Change of Quality Profile
- Change of compiler configuration (include dirs, macros, etc…)
- Change of source checkout filesystem location (there is a dependency on absolute paths)
- Change of system/third party header files