update url #18
Annotations
6 errors and 5 warnings
|
Blackduck Scan
Step detectExecuteScan failed with exit code 1
|
|
Blackduck Scan
failed to execute detect scan - FAILURE_CONFIGURATION => Detect was unable to start because of a configuration issue. Check and fix your configuration.%!(EXTRA *fmt.wrapError=running shell script failed with bash: cmd.Run() failed: exit status 7)
|
|
Blackduck Scan
2026-05-07 09:24:38 UTC ERROR [main] --- Exiting with code 7 - FAILURE_CONFIGURATION
|
|
Blackduck Scan
2026-05-07 09:24:38 UTC ERROR [main] --- Overall Status: FAILURE_CONFIGURATION - Detect was unable to start due to configuration issues. Check and fix your configuration.
|
|
Blackduck Scan
2026-05-07 09:24:36 UTC ERROR [main] --- Detect-Self-Updater: Self-Update of Detect failed due to the following exception. Detect will now continue with existing version.
|
|
Blackduck Scan
Workflow failed! Exit Code: 2 Error from adapter end
|
|
Blackduck Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@c1e323688fd81a25caa38c78aa6df2d33d3e20d9, blackduck-inc/black-duck-security-scan@v2, SAP/project-piper-action@0694c809adf25568fc3c950041097323d71b91ed, stCarolas/setup-maven@d6af6abeda15e98926a57b5aa970a96bb37f97d1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Blackduck Scan
Unexpected input(s) 'scan_mode', valid inputs are ['blackduck_token', 'github_token', 'java-version', 'maven-version']
|
|
Blackduck Scan
TR_DETECT: Failed to create toolrecord file FAILURE_CONFIGURATION => Detect was unable to start because of a configuration issue. Check and fix your configuration.%!(EXTRA *fmt.wrapError=running shell script failed with bash: cmd.Run() failed: exit status 7)
|
|
Blackduck Scan
Failed to generate reports: failed to fetch vulnerabilities: authentication to BlackDuck API failed: request to BlackDuck API failed: HTTP POST request to /api/tokens/authenticate failed: Post "/api/tokens/authenticate": unsupported protocol scheme ""
|
|
Blackduck Scan
Unexpected input(s) 'scan_mode', valid inputs are ['blackduck_token', 'github_token', 'java-version', 'maven-version']
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
bridge_diagnostics_1778145842683
|
423 KB |
sha256:ea2c5d2bf3b8c41a16dfc09c14eb34c5ba05fc708f65ad47871bc732dd8d8579
|
|