FlexNet Code Insight 2019 R3
The following sections provide additional information (such as limitations, requirements, and clarifications) to consider for the various ecosystems supported in the Code Insight Automated Analysis process.
Notes for Supported Go Ecosystems
Note the following for Go ecosystems:
| • | A golang project configured with a supported package manager must include a license file to enable Code Insight to discover it as top-level inventory. |
| • | Currently, Code Insight supports the discovery of top-level inventory only in scans of pre-build Artifact source code. |
| • | If the codebase is uploaded from the release section of the VCS repository, Code Insight must use the version in the name of the project’s parent folder as the version in the top-level inventory name. Any changes to the version in the parent folder name can result in the wrong version being reported in the inventory. |
Notes for Supported Ruby Ecosystems
Note the following for Ruby ecosystems:
| • | For RubyGem projects, Code Insight shows all platform-related dependencies and those dependencies that are not part of a “test” or “dev” group as inventory. Any gems identified as “dev” or “test” are not considered for inventory. |
| • | Only SemVer expressions in the major.minor.patch format are supported to resolve dependencies listed in the manifest file. |
Code Insight parses a .bb file only if it contains an SCR_URI property value that starts with git:// or https://. If the SCR_URI property contains more than one URI, only the first supported URI is considered.
Notes for Supported Git Ecosystems
FlexNet Code Insight scans configuration files inside .git folders encountered in a project codebase and uses identified information to create inventory items.
FlexNet Code Insight 2019 R3 Help LibraryOctober 2019 |
Copyright Information | Flexera |