Default File and Inventory Processing During an Import
FlexNet Code Insight 2019 R3
The following information describes the default behavior for processing files and inventory during an import. (You can modify this default behavior as needed by reconfiguring options, as described in the next section, Available Import Options to Control Import Behavior.)
During an import, the file path (and optionally the MD5) is the key for matching data in the data file with the codebase files for the target project. File paths are matched between the data file to be imported and target codebase files by subtracting the root path from the absolute path, as demonstrated in this example:
|
•
|
Absolute file path—/home/fnci/scanRoot/1/ePortal-1.3/src/gettext.c |
|
•
|
Root path—/home/fnci/scanRoot/1/ |
|
•
|
File path—/ePortal-1.3/src/gettext.c |
The following default logic applies during the import process:
|
•
|
Only those codebase files that have files paths that match in both the data file to be imported and the scanned target codebase based are processed for inventory-to-file association in the target project. See checkInventory (default: false) for more information. |
|
•
|
Only those codebase files that have file paths and MD5s that match in both the data file to be imported and the scanned target codebase are processed when marking files as reviewed in the target project. See checkReviewed (default: true) for more information. |
|
•
|
Only those inventory items whose associated files have file paths that match in both the data file to be imported and the scanned target codebase are processed into the target project. See createEmptyInventory (default: false) for more information. |
Open topic with navigation