VED-1238: Refactor all remaining lambdas deployment to a dedicated pi… #326
Thomas-Boylecontinuous-deployment.yml
on: push
run-quality-checks
/
Lint specification
20s
run-quality-checks
/
Lint Python projects
31s
run-quality-checks
/
Lint Terraform projects
9s
run-quality-checks
/
Test Coverage and SonarCloud
4m 12s
Matrix: deploy-internal-dev-backend / deploy-lambda-images
run-internal-dev-sandbox-tests
/
wait-for-deployment
run-internal-dev-sandbox-tests
/
e2e-automation-tests
run-internal-dev-sandbox-tests
/
publish-test-report
Matrix: deploy-higher-dev-envs
Waiting for pending jobs
Matrix: run-higher-dev-env-tests
Waiting for pending jobs
run-sandbox-tests
/
publish-test-report
Annotations
2 errors and 9 warnings
|
deploy-internal-dev-backend / terraform-plan
Process completed with exit code 2.
|
|
deploy-internal-dev-backend / terraform-plan
Terraform exited with code 1.
|
|
deploy-internal-dev-backend / Deploy delta_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/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-internal-dev-backend / Deploy batch_processor_filter 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/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-internal-dev-backend / Deploy id_sync 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/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-internal-dev-backend / Deploy recordforwarder 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/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-internal-dev-backend / Deploy redis_sync 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/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-internal-dev-backend / Deploy mns_publisher 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/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-internal-dev-backend / Deploy mesh_processor 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/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-internal-dev-backend / Deploy 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/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-internal-dev-backend / Deploy filenameprocessor 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/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~0SGITD.dockerbuild
|
68.6 KB |
sha256:365cce98dfb6d84a64bcd00b4b2307e514014f6776ea638ed00997802d0cc338
|
|
|
NHSDigital~immunisation-fhir-api~1GMRD2.dockerbuild
|
66.4 KB |
sha256:a41e138512cfca477647ce6e7dc94051f750b1d273c5c68534bc9141de89820e
|
|
|
NHSDigital~immunisation-fhir-api~4E448P.dockerbuild
|
67.4 KB |
sha256:70a261b1c040f3af1cd5e02f1ffaef4fb15409fe84f9df953f8d742467304dd9
|
|
|
NHSDigital~immunisation-fhir-api~C3U0VE.dockerbuild
|
68.7 KB |
sha256:918eb149a321218b8779578e7b11d6a6ba67e19b3016f247aa736e5578527fe5
|
|
|
NHSDigital~immunisation-fhir-api~KHB1AT.dockerbuild
|
68.3 KB |
sha256:327246a4ae6b7d093a87e83a2a8badc14af80689690d4690b5e1fd9b7089ecd7
|
|
|
NHSDigital~immunisation-fhir-api~KJMI4L.dockerbuild
|
67.7 KB |
sha256:9efc7efc9989bfb477a207e3936c4a7558a4ebeac7d6b8e50a045994fcdc3fa9
|
|
|
NHSDigital~immunisation-fhir-api~KYPS7A.dockerbuild
|
66.8 KB |
sha256:2b1994c1082bd12cc22dbdf703b540d98b0c778f9edaae672ff30fd3fa47ceca
|
|
|
NHSDigital~immunisation-fhir-api~ML143Z.dockerbuild
|
69 KB |
sha256:4a03c3b853c5a77d55030403f853f1b0e206d5fdc1f1f181998e50b5c2d4ca59
|
|
|
NHSDigital~immunisation-fhir-api~XQT6BL.dockerbuild
|
66.8 KB |
sha256:8bfc4b6cca8816962874cfbd1425e12c80857f8ddd497027c784ce83a7adc6f9
|
|
|
deploy-manifest-ack-backend-dev-internal-dev-1
|
617 Bytes |
sha256:cb0da2fb6313da43895f39e4b38e318bf6ce5952c45719cfde65c4cba3c4c364
|
|
|
deploy-manifest-backend-dev-internal-dev-1
|
608 Bytes |
sha256:b8eccd16c0bda38eaf750809be4efa8a3fe762df9916a0299c53ad66815d5410
|
|
|
deploy-manifest-batch_processor_filter-dev-internal-dev-1
|
652 Bytes |
sha256:18bc8b6a36795eabe1c7eaca02e33d1f9372ad381b4e7be0bfa85fa06fa8e959
|
|
|
deploy-manifest-delta_backend-dev-internal-dev-1
|
627 Bytes |
sha256:4e595845b1cc59ac5a35f00bb036857cc7771af2ad2b3ae115b1e29c7ec1255b
|
|
|
deploy-manifest-filenameprocessor-dev-internal-dev-1
|
635 Bytes |
sha256:023d0e980a38f9b6d49d5958dc4804c6f38cf34b20452479c07b6c569fc0a6d0
|
|
|
deploy-manifest-id_sync-dev-internal-dev-1
|
610 Bytes |
sha256:e83156c1056425c1365a17c41ce38074fc9da4eba8910d54ad9c56bb13791b35
|
|
|
deploy-manifest-mesh_processor-dev-internal-dev-1
|
632 Bytes |
sha256:7c5720d426f0119eae86faac9329542287689bdce7a43d626ff877c9b952530e
|
|
|
deploy-manifest-mns_publisher-dev-internal-dev-1
|
627 Bytes |
sha256:a555442e11cdc741cb89ea0836b955c53c0e8e9615b8f2b8eb2c2499bb3a5781
|
|
|
deploy-manifest-recordforwarder-dev-internal-dev-1
|
631 Bytes |
sha256:d7091561fc9e3555602ddc9fbdc2e4ed59e435c4ebac5d26ffec185ea733aca6
|
|
|
deploy-manifest-recordprocessor-dev-internal-dev-1
|
624 Bytes |
sha256:3a424a960ff26f2ec468e571d43a9034d6242032264025c00541ad1ba001351a
|
|
|
deploy-manifest-redis_sync-dev-internal-dev-1
|
619 Bytes |
sha256:0decac6efed8d2f7fa502aecf3d6cb62224209ac3adfdac99429466dc1f7f4a2
|
|