Rescanning Your Codebase
FlexNet Code Insight 2020 R2
During a codebase scan, FlexNet Code Insight uses a combination of Automated Analysis and Advanced Analysis techniques to identify open-source and third-party code in your product (see About FlexNet Code Insight Scans). Advanced Analysis is performed only if the Compliance Library (CL) has been installed in your Code Insight system and the scan settings for your project have enabled this type of analysis.
Each analysis type runs its own scan. When you run the initial scan on your codebase, both analysis types perform a full scan (that is, a scan on all codebase files). For any subsequent codebase rescan that a user initiates, each analysis type performs either a full rescan, an incremental rescan (that is, a scan on only changed codebase files), or no rescan. The type of rescan executed for an analysis type depends on changes that might have occurred in your codebase, in your scan settings, or with your Code Insight or CL version prior to the rescan.
You always have the option to force a full rescan when necessary if no codebase, scan configuration, or Code Insight version changes have occurred that would normally result in a full rescan. However, keep in mind that a full rescan can be costly.
The following topics provide information you should know about the rescan process and includes instructions on initiating a rescan:
| • | Change Events Resulting in Full or Incremental Rescans |
| • | Effects of Scan-Setting Changes on Rescans |
| • | Handling of Edited Inventory During Rescans |
| • | Initiating a Codebase Rescan |
| • | Forcing a Full Codebase Rescan |