CAST HIGHLIGHT - Code Reader - Results Upload - Manual Upload - csv files that should be excluded from being uploaded to the portal

Once the analysis is done a Zip file and some .csv log files are generated. Only the ZIP  need to be uploaded to the portal, other .csv files are analysis log files and can't be uploaded to the platform.  

Details

A .zip file is generated per scan, containing all application analysis results. Depending on the number of distinct technologies and root source folders, the Agent automatically generates one or several result files with the following naming structure: - FolderName.Technology.date.csv
Eg: myappSRC.PHP.05_29_2015_11_17.csv 

The following screenshot is an example that shows the .csv result files in the zip file that are uploaded.upload.JPG

Only the ZIP  need to be uploaded to the portal, other .csv files are analysis log files (and can't be uploaded to the platform). The Local Agent also generates an analysis log file that allows users to check analysis status for each analyzed source file. This file prepend .csv extension with “ .analysislog ”. These analysis log files should not be uploaded (and will be rejected anyway) by the platform.

If uploading the .zip file do not work for some reason, each .csv result file that need to be uploaded can also be manually uploaded separately but the sequence should be correct. The sequence is normally managed when automatically uploading results. For eg CloudReady result files must be uploaded after the generic technology files. When the ZIP is uploaded this sequence is automatically applied. Analysis log files should be excluded when  csv files are manually uploaded. Only result CSV files located in HLTemporary/analysis folder should be uploaded.


Other CSV files (UnknownTechno.csv, PotentialTechnos.csv, technoFound.csv, etc.) are log files and should not be uploaded to the platform. 

 

To know about the csv files that should be uploaded for each use case please refer https://doc.casthighlight.com/CAST-Highlight-CodeScanBestPractices.pdf

 

NB: Corrupt csv files should not be uploaded. Files with invalid component names such as having null values will not be analysed.

 

Related Articles

CAST HIGHLIGHT - Results Upload - Manual Upload - Fail TECHNOLOGY_SCAN_NOT_FOUND

https://doc.casthighlight.com/CAST-Highlight-CodeScanBestPractices.pdf

CAST HIGHLIGHT - Results Upload - Invalid CSV file error

 

Additional Resources

CAST Highlight Troubleshooting Guides

CAST Highlight Product Documentation

 

Ticket Number

23103, 32827, 51784

 

Have more questions? Submit a request

Comments

  • Avatar

    `Only the ZIP need to be uploaded to the portal, other .csv files are analysis log files (and can't be uploaded to the platform).`

    in a meantime in the screenshot we see `Drop CSV or ZIP files`

    should you change that prompt?

    Edited by Alex Bondarev
  • Avatar

    Once the analysis is done a Zip file and some .csv log files are generated.. Analysis log files can't be uploaded to the platform. If uploading the .zip file do not work for some reason, each .csv result file that need to be uploaded can also be manually uploaded.. Analysis log files should be excluded when csv files are manually uploaded. Only result CSV files located in HLTemporary/analysis folder should be uploaded..
    .
    .

Powered by Zendesk