You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There isn't any logging when waiting for scan completion when queuing scans in the SDK backend, currently, logging in queuing is limited to when the timeout is reached.
We need to have informative logging at least in debug mode so we can understand if we're waiting for a scan to finish before committing a new one or else we can't even understand if we even reach the queuing phase.
My proposal:
Add INFO logging once a scan is queued in the logs here with the scan ID outputted:
This is also related to CxFlow issue 905 enhancement since PRs are not receiving prompt Markdown feedback on whether a scan was queued and/or is still in queue, so that CxFlow knows that the scan is still waiting in queue to be triggered in CxSAST.
The text was updated successfully, but these errors were encountered:
There isn't any logging when waiting for scan completion when queuing scans in the SDK backend, currently, logging in queuing is limited to when the timeout is reached.
We need to have informative logging at least in
debug
mode so we can understand if we're waiting for a scan to finish before committing a new one or else we can't even understand if we even reach the queuing phase.My proposal:
INFO
logging once a scan is queued in the logs here with the scan ID outputted:checkmarx-spring-boot-java-sdk/src/main/java/com/checkmarx/sdk/service/CxService.java
Line 2387 in 19384c3
debug
logging for each 5 or 10 minutes informing that the scan with the given ID of the current project hasn't finished yet here:checkmarx-spring-boot-java-sdk/src/main/java/com/checkmarx/sdk/service/CxService.java
Line 2393 in 19384c3
This is also related to CxFlow issue 905 enhancement since PRs are not receiving prompt Markdown feedback on whether a scan was queued and/or is still in queue, so that CxFlow knows that the scan is still waiting in queue to be triggered in CxSAST.
The text was updated successfully, but these errors were encountered: