Skip to content

[GPCAPIM-395]: Update PDS API secret handling #2943

[GPCAPIM-395]: Update PDS API secret handling

[GPCAPIM-395]: Update PDS API secret handling #2943

Triggered via push April 28, 2026 13:42
Status Failure
Total duration 5m 54s
Artifacts 4
Set CI/CD metadata
7s
Set CI/CD metadata
Commit stage  /  Scan secrets
30s
Commit stage / Scan secrets
Commit stage  /  Check file format
9s
Commit stage / Check file format
Commit stage  /  Check Python format
10s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
19s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
13s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
16s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
59s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
3s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
3m 8s
Test stage / Unit tests
Test stage  /  Contract tests
4m 1s
Test stage / Contract tests
Test stage  /  Schema validation tests
4m 3s
Test stage / Schema validation tests
Test stage  /  Integration tests
4m 6s
Test stage / Integration tests
Test stage  /  Acceptance tests
4m 34s
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

9 errors and 9 warnings
Test stage / Unit tests
Process completed with exit code 2.
Test stage / Contract tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/contract-tests.xml'
Test stage / Contract tests
Process completed with exit code 1.
Test stage / Schema validation tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/schema-tests.xml'
Test stage / Schema validation tests
Process completed with exit code 1.
Test stage / Integration tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/integration-tests.xml'
Test stage / Integration tests
Process completed with exit code 1.
Test stage / Acceptance tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/acceptance-tests.xml'
Test stage / Acceptance tests
Process completed with exit code 1.
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 / 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 / Contract tests
No files were found with the provided path: gateway-api/test-artefacts/. No artifacts will be uploaded.
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/
Test stage / Schema validation tests
No files were found with the provided path: gateway-api/test-artefacts/. No artifacts will be uploaded.
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 / Integration tests
No files were found with the provided path: gateway-api/test-artefacts/. No artifacts will be uploaded.
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 / Acceptance tests
No files were found with the provided path: gateway-api/test-artefacts/. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size Digest
lines-of-code-report.json.zip
898 Bytes
sha256:1fb48a9d8de26acf2540e3c4adfcca2f1e77acb891cda5ab35c239a8fe814935
sbom-repository-report.json.zip
97.7 KB
sha256:5399d12665379f09374e8f87907e49e23d8a44a3d8f40be2880e150a5a83fb31
unit-test-results
9.7 KB
sha256:f4160d44bf16fac49aee829df22e1ed684a63fbfe2054a57bedaba7dc9a78885
vulnerabilities-repository-report.json.zip
4.06 KB
sha256:a51489eafc913d85a4afb43b229a425d4e270e9011b0c03aba9a138da8c19d01