Skip to content

Add use-pr-linker workflow to auto-link PRs to issues #392

Add use-pr-linker workflow to auto-link PRs to issues

Add use-pr-linker workflow to auto-link PRs to issues #392

Triggered via pull request May 25, 2026 10:05
Status Failure
Total duration 4h 40m 26s
Artifacts 3

push-trigger.yml

on: pull_request
build-maven-pre-registration-booking-service  /  maven-build
2m 23s
build-maven-pre-registration-booking-service / maven-build
build-maven-registration-processor-external-integration-service  /  maven-build
2m 24s
build-maven-registration-processor-external-integration-service / maven-build
build-maven-registration-processor-external-stage  /  maven-build
2m 24s
build-maven-registration-processor-external-stage / maven-build
build-maven-cache-provider-hazelcast  /  maven-build
37s
build-maven-cache-provider-hazelcast / maven-build
build-maven-kernel  /  maven-build
3m 5s
build-maven-kernel / maven-build
build-maven-authentication-ref-impl  /  maven-build
4m 27s
build-maven-authentication-ref-impl / maven-build
publish_to_nexus_pre-registration-booking-service  /  publish-to-nexus
publish_to_nexus_pre-registration-booking-service / publish-to-nexus
sonar_analysis  /  maven-sonar-analysis
sonar_analysis / maven-sonar-analysis
Matrix: build-dockers-pre-registration-booking-service
Matrix: build-dockers-registration-processor-external-integration-service
Matrix: build-dockers-registration-processor-external-stage
publish_to_nexus_cache-provider-hazelcast  /  publish-to-nexus
publish_to_nexus_cache-provider-hazelcast / publish-to-nexus
publish_to_nexus_kernel  /  publish-to-nexus
publish_to_nexus_kernel / publish-to-nexus
sonar_analysis_kernel  /  maven-sonar-analysis
sonar_analysis_kernel / maven-sonar-analysis
publish_to_nexus_authentication-ref-impl  /  publish-to-nexus
publish_to_nexus_authentication-ref-impl / publish-to-nexus
sonar_analysis_authentication-ref-impl  /  maven-sonar-analysis
sonar_analysis_authentication-ref-impl / maven-sonar-analysis
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 15 warnings
registration-processor-external-integration-service / build-dockers
Process completed with exit code 1.
registration-processor-external-stage / build-dockers
Process completed with exit code 1.
pre-registration-booking-service / build-dockers
Process completed with exit code 1.
build-maven-registration-processor-external-integration-service / maven-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@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/
build-maven-authentication-ref-impl / maven-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@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/
build-maven-authentication-ref-impl / maven-build
No files were found with the provided path: ./authentication.zip. No artifacts will be uploaded.
build-maven-cache-provider-hazelcast / maven-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@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/
build-maven-cache-provider-hazelcast / maven-build
No files were found with the provided path: ./cache-provider-hazelcast.zip. No artifacts will be uploaded.
build-maven-pre-registration-booking-service / maven-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@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/
build-maven-registration-processor-external-stage / maven-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@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/
build-maven-kernel / maven-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@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/
build-maven-kernel / maven-build
No files were found with the provided path: ./kernel.zip. No artifacts will be uploaded.
registration-processor-external-integration-service / build-docker-warning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
registration-processor-external-integration-service / build-dockers
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, mavrosxristoforos/get-xml-info@1.1.1. 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/
pre-registration-booking-service / build-docker-warning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
registration-processor-external-stage / build-docker-warning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
registration-processor-external-stage / build-dockers
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, mavrosxristoforos/get-xml-info@1.1.1. 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/
pre-registration-booking-service / build-dockers
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, mavrosxristoforos/get-xml-info@1.1.1. 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
pre-registration-booking-service
64.9 MB
sha256:253e75ae14a3e7909bc41536549042067399ef50f922d29b50b9d211d255dd47
registration-processor-external-integration-service
28.5 MB
sha256:cd5b9a3682c59b4ce12ceae9273c134298e77d58809e4205f4b1522e26068036
registration-processor-external-stage
120 MB
sha256:dc54a624a343e60abdbf287891aedcc84a5e83c3605bf83e082e9a8b10e55b03