-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generateScanReport doesn't work with UA Version 21.12.1 #24
Comments
Hi @joaquin386 , we will need more information to evaluate your issue. Thanks! Lena |
You have the case open now at your end. Logs provided where all the above is shown. Still the logs show this:
Seems as the logs is writing the file but then doing a |
in 21.12.2 doesnt work to... |
@joaquin386 did you manage to solve this problem? |
Yes this parameter suddenly was needed after the upgrade. So now it is working and yes the case can be closed. I can do it if you want. |
@joaquin386 Can you tell me where I need to set this parameter? |
@kostukp96 You have the documentation here: https://whitesource.atlassian.net/wiki/spaces/WD/pages/1544880156/Unified+Agent+Configuration+Parameters So either you pass it as an environment variable So you have two options ... whichever fits you best. Closing Issue as problem is solved now. |
@joaquin386 |
Hi
We have the parameter generateScanReport=true and scanReportFilenameFormat=static for UA 21.12.1 and the scan_report.json is not written to whitesource/scan_report.json. We even have this from the logs:
But when checking there is NO folder or NO file with the scan_report.json name.
We had before the upgrade the UA 21.11.2 and the report was generated correctly, we have to disable now the WS scanning because the automation was base on that file.
This started happening the moment UA was upgraded o 21.12.1 (was working on 21.11.2)
BR
Joaquin
The text was updated successfully, but these errors were encountered: