Open Source Security #1529
open-source-security.yml
on: workflow_dispatch
Security
1m 56s
Annotations
9 errors, 2 warnings, and 2 notices
|
Security
Step detectExecuteScan failed with exit code 1
|
|
Security
failed to execute detect scan - FAILURE_POLICY_VIOLATION => Detect found policy violations.: running shell script failed with bash: cmd.Run() failed: exit status 3
|
|
Security
2025-12-10 16:50:06 UTC ERROR [main] --- Exiting with code 3 - FAILURE_POLICY_VIOLATION
|
|
Security
2025-12-10 16:50:06 UTC ERROR [main] --- Overall Status: FAILURE_POLICY_VIOLATION - Detect found policy violations.
|
|
Security
2025-12-10 16:49:10 UTC ERROR [main] --- Automatically trusting server certificates - not recommended for production use.
|
|
Security
2025-12-10 16:49:10 UTC ERROR [main] --- Automatically trusting server certificates - not recommended for production use.
|
|
Security
2025-12-10 16:49:10 UTC ERROR [main] --- Automatically trusting server certificates - not recommended for production use.
|
|
Security
2025-12-10 16:49:09 UTC ERROR [main] --- Automatically trusting server certificates - not recommended for production use.
|
|
Security
2025-12-10 16:48:44 UTC ERROR [main] --- Automatically trusting server certificates - not recommended for production use.
|
|
Security
2025-12-10 16:49:18 UTC WARN [pool-3-thread-1-Stream Redirect Thread] --- WARN: The scan was not executed since the latest scan for this code location was performed 13 hours ago, which is less than minimum scan interval 24 hours configured through global setting. Consider decreasing minimum interval between scans by changing global setting value for minimum scan interval or --min-scan-interval command line option. Note that --min-scan-interval option overrides global setting.
|
|
Security
The useDetect9 option is deprecated
|
|
Security
💡 BlackDuck Detect found policy violations. Review security policies and fix compliance issues.
|
|
Security
💡 BlackDuck Detect found policy violations. Review security policies and fix compliance issues.
|