Gerrit Composed Maven Merge #106
onap-githubgerrit-merge.yaml
on: workflow_dispatch
notify
15s
run-maven-clm
/
run-maven-clm
23m 37s
run-maven-sonar
/
run-maven-sonar-cloud-scan
17m 6s
report-status
10s
Annotations
2 errors and 4 warnings
|
run-maven-sonar / run-maven-sonar-cloud-scan
Cannot invoke "io.micrometer.core.instrument.Counter.increment()" because the return value of "io.micrometer.core.instrument.MeterRegistry.counter(String, java.lang.Iterable)" is null
|
|
run-maven-clm / run-maven-clm
Cannot invoke "io.micrometer.core.instrument.Counter.increment()" because the return value of "io.micrometer.core.instrument.MeterRegistry.counter(String, java.lang.Iterable)" is null
|
|
notify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: shimataro/ssh-key-action@d4fffb50872869abe2d9a9098a6d9c5aa7d16be4. 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/
|
|
run-maven-sonar / run-maven-sonar-cloud-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, infovista-opensource/vars-to-env-action@3d3e7c8ae1e9e5fcd9ce83e56ab85a6a135d2ffa, stCarolas/setup-maven@d6af6abeda15e98926a57b5aa970a96bb37f97d1. 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/
|
|
run-maven-clm / run-maven-clm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, infovista-opensource/vars-to-env-action@3d3e7c8ae1e9e5fcd9ce83e56ab85a6a135d2ffa, stCarolas/setup-maven@d6af6abeda15e98926a57b5aa970a96bb37f97d1. 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/
|
|
report-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: shimataro/ssh-key-action@d4fffb50872869abe2d9a9098a6d9c5aa7d16be4, technote-space/workflow-conclusion-action@v3. 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/
|