Comparison of Standard and Inventory-Only Imports

FlexNet Code Insight 2019 R3

The data that is imported is controlled by the Type of the target project (that is, the project to which data is imported). For example, if the project was created as a standard project (that is, its Type attribute is Standard), then the import will be a standard import. If the project was created as an inventory-only project (that is, its Type attribute is Inventory Only), then the import will be an inventory-only import.

The following table highlights the basic differences between the two import types.

Comparison of Standard and Inventory-Only Imports

Import Behaviors and Usage

Standard Import

Inventory-only Import

Import scope

Performs a full import (that is, both inventory and codebase files are processed):

• Processes all inventory items (published and unpublished).
• Per inventory item, provides inventory details, status, and associated repository item (component-version-license).
• Lists associated file paths for inventory.

Performs a partial import:

• Processes inventory only.
• Does not process codebase files (reviewed or unreviewed).

File processing

Does the following:

• Processes all files marked as reviewed in the data file to be imported.
• Provides absolute file paths and MD5s for processed files.
• Does not import unreviewed files.

Does not process files (reviewed or unreviewed).

Custom-data processing

Imports custom versions, custom licenses, and custom mappings.*

Imports custom versions, custom licenses, and custom mappings.*

Required type for target project

Requires a project created with the Standard attribute.

Requires a project created with the Inventory Only attribute.

Target project codebase requirement

Requires a codebase that is uploaded (or synchronized) to the target project and scanned.

Requires no codebase.

Access to imported inventory and codebase files

Provides direct access to the following:

• Imported inventory through Project Inventory and Analysis Workbench.
• Imported codebase files through Analysis Workbench.

Provides direct access to imported inventory through Project Inventory. (Access to inventory and codebase files through Analysis Workbench is not available.)

Usage

Produces a full project copy that can be used for the following (for ongoing scanning and analysis):

• Full project backups.
• Application of analysis work from one product version to another (branching).
• Application of analysis work from one project version to another.

Provides a means to create inventory from the following:

• An external system.
• A Code Insight inventory-only project that is configured to scan remotely using a Jenkins or other scan agent plugin.

* The import does not process custom components. Instead, FlexNet Code Insight creates target inventory of the work-in-progress (WIP) type or license-only type to represent inventory with custom components.

FlexNet Code Insight 2019 R3 Help Library

October 2019

 Copyright Information | Flexera

Open topic with navigation