Skip to content

Spring Cloud Function CI Job #6

Spring Cloud Function CI Job

Spring Cloud Function CI Job #6

Triggered via schedule March 18, 2026 00:34
Status Success
Total duration 10m 38s
Artifacts

ci.yaml

on: schedule
Matrix: deploy / build
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 6 warnings
deploy / Build main (JDK 21)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 21)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 21)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 21)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 25)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 25)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 25)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 25)
Failed to bind on [0.0.0.0:8080]
deploy / Build 4.3.x (JDK 21)
Failed to bind on [0.0.0.0:8080]
deploy / Build 4.3.x (JDK 21)
Failed to bind on [0.0.0.0:8080]
deploy / Build 4.3.x (JDK 21)
Failed to bind on [0.0.0.0:8080]
deploy / Build 4.3.x (JDK 21)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 17)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 17)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 17)
Failed to bind on [0.0.0.0:8080]
deploy / Build main (JDK 17)
Failed to bind on [0.0.0.0:8080]
deploy / Build 4.3.x (JDK 17)
Failed to bind on [0.0.0.0:8080]
deploy / Build 4.3.x (JDK 17)
Failed to bind on [0.0.0.0:8080]
deploy / Build 4.3.x (JDK 17)
Failed to bind on [0.0.0.0:8080]
deploy / Build 4.3.x (JDK 17)
Failed to bind on [0.0.0.0:8080]
deploy / setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
deploy / Build main (JDK 21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, docker/login-action@v3, s4u/maven-settings-action@v3.0.0. 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/
deploy / Build main (JDK 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, docker/login-action@v3, s4u/maven-settings-action@v3.0.0. 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/
deploy / Build 4.3.x (JDK 21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, docker/login-action@v3, s4u/maven-settings-action@v3.0.0. 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/
deploy / Build main (JDK 17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, docker/login-action@v3, s4u/maven-settings-action@v3.0.0. 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/
deploy / Build 4.3.x (JDK 17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, docker/login-action@v3, s4u/maven-settings-action@v3.0.0. 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/