Skip to content

initial commit

initial commit #2963

Triggered via push April 29, 2026 10:31
Status Failure
Total duration 2m 35s
Artifacts 8
Set CI/CD metadata
4s
Set CI/CD metadata
Commit stage  /  Scan secrets
6s
Commit stage / Scan secrets
Commit stage  /  Check file format
6s
Commit stage / Check file format
Commit stage  /  Check Python format
6s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
9s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
11s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
14s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
45s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
3s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
42s
Test stage / Unit tests
Test stage  /  Contract tests
1m 10s
Test stage / Contract tests
Test stage  /  Schema validation tests
1m 19s
Test stage / Schema validation tests
Test stage  /  Integration tests
1m 8s
Test stage / Integration tests
Test stage  /  Acceptance tests
1m 7s
Test stage / Acceptance tests
Test stage  /  Merge test coverage
0s
Test stage / Merge test coverage
Test stage  /  SonarCloud Analysis
0s
Test stage / SonarCloud Analysis
Build stage  /  Artefact 1
Build stage / Artefact 1
Build stage  /  Artefact 2
Build stage / Artefact 2
Acceptance stage  /  Environment set up
Acceptance stage / Environment set up
Acceptance stage  /  Load test
Acceptance stage / Load test
Acceptance stage  /  Security test
Acceptance stage / Security test
Acceptance stage  /  UI performance test
Acceptance stage / UI performance test
Acceptance stage  /  UI test
Acceptance stage / UI test
Acceptance stage  /  Environment tear down
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
Test stage / Schema validation tests
Process completed with exit code 2.
Test stage / Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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/
Test stage / Acceptance tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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/
Test stage / Integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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/
Test stage / Contract tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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/
Test stage / Schema validation tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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
acceptance-test-results
113 KB
sha256:b8ec535cf84839643c5fa2d38a2b0438d647f05bd83fd3664cc58c2c3e463e23
contract-test-results
117 KB
sha256:a4c2a4bedcb9098ff7fdf2714110be1bf4f46052c2434c10e4e6d177b41df215
integration-test-results
115 KB
sha256:782e87545b4ef6cc2fa6033fd0c4cf2f0d9b81171437614b387520cab6487b3b
lines-of-code-report.json.zip
870 Bytes
sha256:ee5c907beb40b835d60c0f9f06d4c47dc85dde359521c61f7574bfdd093c1456
sbom-repository-report.json.zip
96.7 KB
sha256:62fbe9a25e213a096808b2a07b9fc6455478b3488f6b592f85fced5e58b398e2
schema-test-results
113 KB
sha256:213239e27180069080fb6ad786c104b447ed01f20bd5f5e7cf4cf6304ad80fb2
unit-test-results
236 KB
sha256:5aa3a15d262d8364ba40e1a1326988b1f5402eef6dc5e1a80494a3a74f2fb8b0
vulnerabilities-repository-report.json.zip
4.03 KB
sha256:54f68f4511a261a7ecd74bae2bfaaf98dcf7ab3406df10ec7867ecdf195aa018