Click to enlarge
To add source code:
- Drag and drop one .zip or .tar.gz file containing your source code - or click the upload cloud icon to add a file using a traditional "open file" method. Please ensure that your source code archive does NOT contain any other archive files - this can cause the analysis process to fail.
- If you have configured a source code folder (see Administration Center - Settings - Source Folder Location) you can click the yellow folder to add code directly from this folder - only one folder in the designated path can be selected:
If you want to deliver source code containing:
- .NET source code: you should ensure that you define the location of the .NET Assemblies which is required for a successful analysis. See Configuring source code delivery for .NET.
- Maven based source code: you should ensure that you define the location of the Maven repositories so that any associated JAR files can be automatically discovered and that POM dependencies can also be located - which is required for a successful analysis. See Configuring source code delivery for Maven.
When you have made your option choices (see below), click either:
- PROCEED, any subsequent steps will be skipped and:
- if the Run Analysis option is disabled, the version will be added and will appear in the Application - Versions screen.
- if the Run Analysis and the Publish to CAST Imaging options are enabled, the analysis/publishing will be actioned immediately.
- NEXT, see Manage Exclusions.
|Version Name||Enter a name for the Version. Default name will be set to: Version-YYYY-MM-DDTHH-MM-SS.|
|Version Date||Enter a date for the Version. Default date will be set to YYYY-MM-DD HH:MM.|
Unticked by default. Selecting the option will cause the Application to be backed up as part of the actions you choose. When adding a new version for a new Application, enabling this option is not necessary since there is nothing to back up. When the option is enabled, some additional processing time is required while the backup completes. Backups are stored in the following location on the relevant AIP Node and can be managed in Administration Center - Applications - Application Details:
|Same configuration as previous version|
|Enable Automatic discovery|
Only available when adding a new version when a version already exists and when the option Same configuration as previous version (see above) is enabled - i.e. a "rescan" scenario. See Application rescan for CAST Imaging for more information.
Choose whether you want to run an analysis immediately after the source code is delivered. Technically the Run analysis option also includes an internal step called "Prepare analysis data" step, which allows:
For a Standard onboarding scenario, you should enable this option. Enabling this option includes the following steps that would otherwise need to be manually actioned:
Enabling the option will also automatically expose the following options:
For a step-by-step onboarding scenario, you should disable this option. This will allow you to work through the process of validating/accepting the version, running an analysis and publishing to CAST Imaging as separate steps.
This option allows you to choose the Module strategy for your results. Modules are used as a means to configure analysis results into meaningful groups or sets for display purposes - indeed CAST Imaging has a dedicated Modules view mode. The content of a module is based on source code.
CAST offers these options when creating a new version:
|Publish to CAST Imaging|
Choose whether you want to publish the data in your CAST Imaging instance immediately after the source code is delivered. This option is enabled by default:
For a Standard onboarding scenario, you should enable this option.
For a step-by-step scenario, you should disable this option. This will allow you to work through the process of validating/accepting the version, running an analysis and publishing to CAST Imaging as separate steps.