Source Code Management (SCM) Support

This release includes the following enhancement to Source Code Management (SCM):

•

Ability to Synchronize Folders from Git Repositories on Scan Server

To efficiently manage large codebases in Git repositories, Code Insight now allows you to synchronize required folders or subfolders from Git branches, Git tags, or Git commits in a Git repository to designated locations on the Scan Server for scanning.

This enhancement enables you to define Git repository URLs—including the required folder names—within an SCM Git instance for the synchronization process. As a result, the folders from different locations within a Git repository are synchronized to the defined locations on the Scan Server. The following outlines the formats to specify a Git repository URL—with a folder name—in an SCM Git instance:

•

For a specific folder in a Git repository, prefix the folder name with “**”. For example:

git@git.eng.flexera.com:org1/repo1.git**Folder1

•

For a specific folder inside a subdirectory of a Git repository, prefix the “folderName/subfolderName” with “**”. For example:

git@git.eng.flexera.com:org1/repo1.git**Folder1/SubFolder1

•

For a specific folder in a specific branch, prefix the branch name with”~~” and then the folder name with “**”. For example:

git@git.eng.flexera.com:org1/repo6.git~~BranchB**Folder2

•

For a specific folder in a specific tag, prefix the tag name with “^^” and then the folder name with “**”. For example:

git@git.eng.flexera.com:org1/repo7.git^^v1.0.4**Folder3

•

For a specific folder in a specific commit, prefix the commit ID with “>>” and then the folder name with “**”. For example:

git@git.eng.flexera.com:org1/repo8.git>>337b811c76f9dff572d53d9d42e1163aaadb9549**Folder4

For more information, see Fields Used to Configure a SCM Git Instance in the Code Insight User Guide.