DMT - Package Configuration tab - Where is your source code?

Package Configuration tab - Where is your source code?

Note that changes you make to this section once the source package has been packaged will require you to regenerate the source package.

This section defines how the CAST Delivery Manager Tool accesses the source code you want to extract and include in a Source Code Package for analysis. It differs depending on the type of Source Code Package you are configuring:

• Database
• Source Code Management system (SCM)
• Specific Repository
• Others

Other options common to some of the above Source Code Package configuration options are available and are described below:

• Advanced extraction settings

Database

These options correspond to the selection of one of the "database" options when you add a new source code package:

The configuration options differ depending on the type of database you choose in the wizard:

Source Code Management System

These options correspond to the selection of one of the "SCM based" options when you add a new source code package:

The configuration options differ depending on the option you choose in the wizard:

Specific Repository

These options correspond to the selection of one of the "vendor specific repository" options when you add a new source code package:

The configuration options differ depending on the option you choose in the wizard:

Others

These options correspond to the selection of one of the "file/folder based" options when you add a new source code package:

The configuration options differ slightly depending on the options you choose in the wizard. Select the appropriate option below for more information:

Advanced extraction settings

This section is common to certain packages and enables you to:

• limit the extraction to specific folders in the target
• ignore certain folder paths or file types during the extraction process. This can be useful if your source code target contains items that you do not want to include (for example, test source code or batch files for example).

If you do not enter anything in these sections, the CAST Delivery Manager Tool will simply extract ALL projects it finds in the target root path and sub-folders and these will ALL be automatically transformed into Analysis Units in the CAST Management Studio should any projects be discovered.

Folders to extract

This section enables you to limit the extraction to specific folders: This button will browse the target folder/SCM (for the SCM, using the credentials you supplied) and display a list of the folders that are available. Place a check mark next to the folder or folders that you want to extract: Please note that you may receive "Browse" warnings if you attempt to expand a "deep" folder tree too quickly. Please ensure that the folder hierarchy has fully displayed before you attempt to browse deeper. Use this button to add a new folder path (it must be a relative path): A dialog box will be displayed allowing you to enter the relative path of the folder you are targeting. For example if your source code is located in D:\CODE, and you want to specifically target D:\CODE\com.company.tool\src, then you need to enter "com.company.tool\src" in the dialog box. The CAST Delivery Manager Tool will recursively search ONLY this location. You can only enter one location at a time using this option - to enter multiple locations, either repeat the Add New Location action, or use the option below. Use this button to edit an existing folder path - a dialog box will appear in which you can modify the existing folder path. Use these icons to change the order in which the selected folders are packaged (when using the Package action at Version level). This is useful if resources in folder A rely on resources in folder B. Use this button to remove an existing folder path from the list.

Folders or files to ignore

This section enables you to ignore certain folder paths or file types during the extraction process. The strings you enter need to be in Regular Expression format (see Use Regular Expressions for more information about this) - any string that is matched during the extraction will be ignored. Use this button to add a new Regular Expression - a dialog box will appear and you can enter the Regular Expression. See Use Regular Expressions for more information about the dialog box. Notes You can only enter one Regular Expression at a time. Use this button to edit an Regular Expression you have already added - a dialog box will appear in which you can modify the existing Regular Expression. Use these icons to change the order in which the ignored folders/files are scanned. Use this button to remove an existing Regular Expression from the list. Use these buttons to facilitate the reuse of exclusion configuration patterns across multiple platforms. You can export the configuration to .CSV file import a configuration from .CSV file When importing a configuration from a .CSV file, the new configuration patterns will be added to any configuration patterns that have already been defined. In other words, existing patterns will not be removed. Please note that if you exclude a folder and subsequently during the Package action the discoverer finds a reference to the excluded folder, then a Package Alert (see Package Alert tab - Packaging alerts) will be generated. There is no way to resolve this alert with a manual remediation (see Package Alert tab - Packaging alerts - Creating a Manual Remediation), as such, if you still need to exclude the folder and want to avoid an alert, you can exclude its contents only using a specific Regular Expression: For example, you have a subfolder entitled "unittests" that you do not want to include in the Package - you exclude this folder. However, other code in the Package references this folder and as such a Package Alert will be generated when the Package action is run. Use forward slashes around the folder name in your Regular Expression to force the CAST Delivery Manager Tool to ignore the contents of the folder but keep the folder itself: /unittests/ No Package Alert should be generated.