Basic Requirements for the Upload
The following are basic requirements for a codebase upload:
|
•
|
The Scan Server to which you are uploading the codebase must be running (that is, the Tomcat server installed on the same instance as the Scan Server must be running). |
|
•
|
Any archives that you want to expand within the codebase must be ones that the upload process supports for expansion. See Expandable Archives. |
|
•
|
The size limit for the codebase you are uploading is 10 GB. |
Although the 10 GB size limit for an upload cannot be changed, methods are available for providing a larger project codebase for scanning on the Scan Server. See the next section, Codebase Size Limitations for Uploads and Scans, for more information.
Codebase Size Limitations for Uploads and Scans
The size limit for a codebase upload is 10 GB and cannot be changed. However, the size of the project codebase that is actually scanned can be greater than 10 GB if you apply any of the following scenarios:
|
•
|
Upload multiple 10 GB (or less) codebases in separate uploads for the same project (without overwriting previous files). |
|
•
|
Synchronize a codebase repository that is greater than 10 GB to the Scan Server (from Git, Subversion, or Perforce) using the Source Code Management functionality, as described in Configuring Source Code Management). |
|
•
|
Copy codebase files directly to the scan root (assuming you have access to the file system on the Scan Server). |
Code Insight has been tested and is certified to successfully scan codebases that are within the following size limitations:
|
•
|
When Code Insight uses a MySQL database, any codebase up to 35 GB in size and containing no more than 700,000 files. |
|
•
|
When a SQL Server database is used, any codebase up to 15 GB in size and containing no more than 300,000 files. |