Skip to content

SCANJLIB-306 Restore authentication support for proxy + SSL #57

SCANJLIB-306 Restore authentication support for proxy + SSL

SCANJLIB-306 Restore authentication support for proxy + SSL #57

Triggered via pull request March 10, 2026 17:28
Status Failure
Total duration 22m 15s
Artifacts 2

build.yml

on: pull_request
Matrix: qa
Promote
0s
Promote
Fit to window
Zoom out
Zoom in

Annotations

1 error and 8 warnings
QA - SQ LATEST_RELEASE[2025.1]
Process completed with exit code 1.
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache/save@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
QA - SQ LATEST_RELEASE[2025.1]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
QA - SQ LATEST_RELEASE
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
QA - SQ LATEST_RELEASE[2026.1]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.

Artifacts

Produced during runtime
Name Size Digest
server-logs-qa-2
16.8 KB
sha256:90562c720b4fe69c0ab4c60f87d71a2e65b1cc5b3196394450a23cfd95300722
test-results-qa-2
18.5 KB
sha256:0ac3af7a0b5f6d69c81279d51d794fb35d61796cbddedac3b16f1b1eaa671180