Export/Import Processes with Legacy Projects
Previous to Code Insight 2020 R3, projects were one of two types—standard or inventory-only. A standard project managed the results of a server scan—that is, a scan performed by the Scan Server on a codebase that was uploaded or synchronized to the Scan Server. The inventory-only project managed the results of a remote scan, performed by a scan agent on a remote codebase. (The agent sent the scan results to the project on the Code Insight server.) The scan results in both project types included an inventory of open-source and third-party software. Additionally, scan results in the standard project included information about the codebase files, enabling users to perform file operations. The inventory-only project, however, included no information about the remote codebase files.
Beginning with Code Insight 2020 R3, all scanning—server and remote—is accomplished in a single “unified” project, simply called “project” in this documentation. In addition to an inventory of open-source and third-party software, the new project type can include information about codebase files from both server and remote scans, enabling file operations on all project files.
Migration to the New Project Type
During an upgrade from a pre-2020 R3 Code Insight release to the current release, standard projects are automatically migrated to the new project type.
Inventory-only projects, now called legacy projects, continue to be supported with limitations. For example, these projects support only 2020 R2 or earlier scan-agent plugins and allow imports only from other legacy projects. Note that legacy projects will be deprecated in the future.
If you want to migrate an legacy project to the new project type, see the following Knowledge Base article in the Revenera Community:
New Export JSON Elements
Starting in Code Insight 2020 R3, the JSON output for an export process run contains the following elements to support remote codebase-file information that can be exported from a Code Insight project created in 2020 R3 or later:
| • | remoteAlias— The unique name for a remote scan agent used by the project |
| • | remoteScanFolders—A list containing the scan root for each alias |
| • | remoteFilePaths (for inventories)—The list of all remote file paths associated with inventory |
| • | remoteReviewedPaths—The list of all reviewed remote files |