Why do my generated Polyspace Access logs (via Jenkins script) only contain STDOUT and are missing ERROROUT details?

When using a command to generate Polyspace Access log files via a Jenkins script for the Polyspace analysis server this log file does NOT include the ERROROUT info.

>"C:\Program Files\MATLAB\Polyspace Server\R2020b\polyspace\bin\polyspace-access.exe" -protocol http -host host.address..com -login username -encrypted-password ******** -upload Polyspace/BF/xyz -project my_project -log Polyspace/Access/Log/upload.log  1>Polyspace/Access/Cmd/upload.txt

So, my question is, what can we do on the analysis server side to trigger the errorout info, too?

Answer 1

[MathWorks Support Team]

Obtaining the ERROROUT information is essential to analyze any Polyspace Access issues. STDOUT is not sufficient.

You could for example use the scripts provided in this MATLAB Answers post to get the logs:

https://www.mathworks.com/matlabcentral/answers/523796-how-to-debug-an-upload-download-issue-when-using-polyspace-access

For generating own Jenkins logs:

"polyspace-access.exe [...] -log <filename>.log >1 [...]"

redirects only STDOUT (because of ">1")

=> The recommandation is to not redirect because the -log option already does the job:

polyspace-access.exe [...] -log <filename>.log