Skip to content

Add global retry limit (#298) #113

Add global retry limit (#298)

Add global retry limit (#298) #113

Triggered via push May 15, 2026 18:32
Status Success
Total duration 9m 39s
Artifacts 18

java-ci.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
build
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, gradle/actions/setup-gradle@v4. 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/
unit_test
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, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. 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/
producer_only_test
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, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. 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/
redis_cluster_test
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, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. 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/
nats_integration_test
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, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. 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/
integration_test
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, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. 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/
reactive_integration_test
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, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. 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/
coverage_report
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/download-artifact@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. 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/

Artifacts

Produced during runtime
Name Size Digest
coverage-integration
738 KB
sha256:851c3e264b89fbc2c76042d3dde433add46fe89437496022ea913572d7b03031
coverage-nats
315 KB
sha256:cc2f0ac0e16021fdd566ba58416e1f2110357a6c2e21f8fa6649989595795c50
coverage-producer
314 KB
sha256:d7a601310e82a774768ff157fe8c690b94738fd18f96e424c94aa7a6163d31c9
coverage-reactive
568 KB
sha256:e0359d4817b86380c6274fcbf5453480fc3290746331c755e0999bac4c6b0524
coverage-redis-cluster
524 KB
sha256:68b35a5431590ec8ae126b10d3017e563ea1a9f3f470e1df771d7b5ae3e5f953
coverage-report
1.35 MB
sha256:f4cc812e73c47bcc3395bc09a5cacb3ebdb433429d60ede728822ead0d36ec0e
coverage-unit
513 KB
sha256:c4ecfaccb439be7d7a711349595f06997663665f2dc12979967c6329cd7cfded
integration-redis-server
734 Bytes
sha256:4195b243d76d487d88966c0c7869b86ce35705b20db18c503bbeddf9d85539f2
integration-test-results
29.7 KB
sha256:c09b783f7d806a1ba90e347f53fda7f91272697b169ba5095f801c1130993c80
nats-server
855 Bytes
sha256:e6de91874c8be5d13ebc42baf2912b03b6f3b2dae3b13007d7b33d2918bcdda1
nats-test-results
57.3 KB
sha256:7ba4e9cc9284580834f076584d36ddcec38b3876e6a312a99a0febcecfeb333c
producer-redis-server
603 Bytes
sha256:fa8afe50a8b640950ea4f8a32c3dbe1586ce5734498106747ec08ebc88d834f0
producer-test-results
2.17 KB
sha256:77d4be4a2b2c6c002c02c83f00075a2133fd33b030aad4750091c98745ae0050
reactive-integration-test-results
28.2 KB
sha256:1d343f2a3d52ce4bfdc5681ea5d6901e3dd4a45a8d1d2ee1adabb3ec5f0201cb
reactive-redis-server
734 Bytes
sha256:4e8b574fa672119b798d898f1b38aad7b750e92ad954890c8a0ccb46c149d15a
redis-cluster-test-results
6.07 KB
sha256:0ddf3ecf6ce21095713fed443af69c40b44bcf80e49e726488156ed8b3f046bc
redis-server-cluster
8.09 KB
sha256:3900fec60b6597ee97dbaffab22913071efaf416aa6ac426f8e9c4b1c0ee5653
unit-test-results
46.7 KB
sha256:18fa56e520124c3678b36a998281b954a06f097d3b8e09fcda6c2224ea316b28