Even if a bug does slip in, it will be caught and fixed in time. ![]() It is to track such cases that the second security level - regular static analysis on the build server - is needed. However, this solution does not guarantee that defects will never get to the version control system. We recommend using the incremental analysis mode, which allows you to have analysis automatically initiated only for recently modified code after the build. For that reason, you want to find and fix bugs as soon as possible, and running PVS-Studio on the developers' machines makes this easier. This concept stems from the fact that the earlier a defect is detected, the less expensive and difficult it is to fix. A better solution is to build a system that could perform source code analysis at two levels: locally on the developers' machines and on the build server. How to use static analysis most efficientlyīefore talking on the subject of this article, it would be useful for you to know that running PVS-Studio solely on the build server is effective yet inefficient. Integration into the CI process on Linux is discussed in the article " How to run PVS-Studio on Linux". This article discusses integration of PVS-Studio into the continuous integration process on Windows.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |