VED-1238: Refactor all remaining lambdas deployment to a dedicated pipeline stage #2254
Thomas-Boylepr-deploy-and-test.yml
on: pull_request
run-quality-checks
/
Lint specification
23s
run-quality-checks
/
Lint Python projects
33s
run-quality-checks
/
Lint Terraform projects
7s
run-quality-checks
/
Test Coverage and SonarCloud
4m 1s
Matrix: deploy-pr-backend / deploy-lambda-images
Matrix: run-e2e-automation-tests
Waiting for pending jobs
Annotations
9 errors and 2 warnings
|
deploy-pr-backend / Deploy backend image / Build or reuse image
Process completed with exit code 254.
|
|
deploy-pr-backend / Deploy mns_publisher image / Build or reuse image
Process completed with exit code 254.
|
|
deploy-pr-backend / Deploy redis_sync image / Build or reuse image
Process completed with exit code 254.
|
|
deploy-pr-backend / Deploy batch_processor_filter image / Build or reuse image
Process completed with exit code 254.
|
|
deploy-pr-backend / Deploy delta_backend image / Build or reuse image
Process completed with exit code 254.
|
|
deploy-pr-backend / Deploy id_sync image / Build or reuse image
Process completed with exit code 254.
|
|
deploy-pr-backend / Deploy mesh_processor image / Build or reuse image
Process completed with exit code 254.
|
|
deploy-pr-backend / Deploy recordforwarder image / Build or reuse image
Process completed with exit code 254.
|
|
deploy-pr-backend / Deploy filenameprocessor image / Build or reuse image
Process completed with exit code 254.
|
|
deploy-pr-backend / Deploy ack-backend image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
|
|
deploy-pr-backend / Deploy recordprocessor image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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 | |
|---|---|---|---|
|
NHSDigital~immunisation-fhir-api~1NRZEH.dockerbuild
|
38.2 KB |
sha256:16ba0cc09edea3ca60ce0f4eb34645719586c443919d447f0accfe51308ca806
|
|
|
NHSDigital~immunisation-fhir-api~RFFSBL.dockerbuild
|
39 KB |
sha256:b7637ee0cd29d7539df10b76512cdea3a39c4dd6c3f48d61b7b5faac7625a170
|
|
|
deploy-manifest-ack-backend-dev-pr-1414-1
|
624 Bytes |
sha256:f2a3119c698369df97f51dd6dc907c1f0936151800febc8821ffbfc070efc500
|
|
|
deploy-manifest-recordprocessor-dev-pr-1414-1
|
630 Bytes |
sha256:5e5eceed8572bebaccbd48dd941eb74cb3adc92a8782cc676f59152cfdaf5ec5
|
|