In a large C ++ project, transparency analysis reports problems in files that we will not fix, for example. Boost libraries, STL headers, some third-party libraries, etc. Ideally, there is a mechanism for completely ignoring these and so as not to increase the total counter for such problems.
In Coverity Connect (v8.1), we configured Components with file regular expression and filter the corresponding files well when viewing, but the total number of problems does not fall. Two questions related to this:
- Is there a way to remove the number of common problems for files that we do not need? for example, after such a problem has already been fixed
- if the new code we introduce includes one of the abusive boost / STL / etc headers, will this synchronize a common problem counter? (obviously this would be less desirable).
source share