Change Events Resulting in Full or Incremental Rescans
FlexNet Code Insight 2020 R2
The following table shows the types of change events that result in a full or an incremental rescan for Automated Analysis and Advanced Analysis should you initiate a rescan on your codebase:
|
Changes to... |
Automated Analysis |
Advanced Analysis |
Notes |
|
Codebase files |
Incremental rescan |
Incremental rescan |
Changes in codebase files are determined by the MD5 hash digest of the files. |
|
Automated Analysis rule set |
Full rescan |
No rescan |
Rules are automatically pushed to your Code Insight server through an internal process and the weekly Electronic Update. Note • Custom detected rules are applied only during the initial codebase scan and during a forced full rescan. These rules are not applied during a normal rescan, whether incremental or full. |
|
FlexNet Code Insight version |
Full rescan |
No rescan |
This change usually involves an upgrade in the Code Insight version. |
|
Scan profile settings |
Full rescan |
Full rescan |
Depending on the scan profile settings that were changed, one or both analysis types will perform a full rescan. Note that changes to settings that apply to source-code matching result in an expensive Advanced Analysis full rescan. See Effects of Scan-Setting Changes on Rescans for more information. Scan profiles are configured by the Administrator as described in the FlexNet Code Insight Installation and Configuration Guide. |
|
CL version |
No rescan |
Full rescan |
This change is associated with a change to the CL Path value identified in the Scan Server setup. (This setup is handled by the Administrator, as described in the FlexNet Code Insight Installation and Configuration Guide.) |