SONARJAVA-6216 Optimize CI to reduce Repox bandwidth for sonar-java: add timeouts #1275
build.yml
on: pull_request
Build
1m 57s
Build and Unit Test on Windows
7m 49s
Matrix: Plugin QA
Matrix: Ruling QA
Sanity Test
4m 7s
Test Analyze
13m 10s
Custom Rules and License Check
7m 26s
Autoscan Tests
10m 54s
Promote
18s
Annotations
22 warnings
|
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Sanity Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Ruling QA (github-ubuntu-latest-m, only-sonarqube-project)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, hashicorp/vault-action@7709c609789c5e27b757a85817483caadbb5939a, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Build and Unit Test on Windows
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Ruling QA (github-ubuntu-latest-m, without-sonarqube-project)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, hashicorp/vault-action@7709c609789c5e27b757a85817483caadbb5939a, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Custom Rules and License Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Plugin QA (DEV, 21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, hashicorp/vault-action@7709c609789c5e27b757a85817483caadbb5939a, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Plugin QA (LATEST_RELEASE, 21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, hashicorp/vault-action@7709c609789c5e27b757a85817483caadbb5939a, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Autoscan Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Ruling QA (github-windows-latest-m, without-sonarqube-project)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, hashicorp/vault-action@7709c609789c5e27b757a85817483caadbb5939a, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Test Analyze
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Ruling QA (github-windows-latest-m, only-sonarqube-project)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, hashicorp/vault-action@7709c609789c5e27b757a85817483caadbb5939a, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566, runs-on/cache@50350ad4242587b6c8c2baa2e740b1bc11285ff4, SonarSource/gh-action_cache/credential-guard@v1, SonarSource/gh-action_cache/credential-setup@v1. 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/
|
|
Promote
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5228313ee0372e111a38da051671ca30fc5a96db. 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/
|