Skip to content

[GPCAPIM-289]-[Pass integration tests through APIM proxy (with mock CIS2)]-[RP] #1677

[GPCAPIM-289]-[Pass integration tests through APIM proxy (with mock CIS2)]-[RP]

[GPCAPIM-289]-[Pass integration tests through APIM proxy (with mock CIS2)]-[RP] #1677

Triggered via pull request March 10, 2026 15:13
Status Failure
Total duration 2m 37s
Artifacts 8

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
7s
Set CI/CD metadata
Commit stage  /  Scan secrets
10s
Commit stage / Scan secrets
Commit stage  /  Check file format
8s
Commit stage / Check file format
Commit stage  /  Check Python format
11s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
3s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
12s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
15s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
10s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
1m 3s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
5s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
34s
Test stage / Unit tests
Test stage  /  Contract tests
1m 5s
Test stage / Contract tests
Test stage  /  Schema validation tests
1m 15s
Test stage / Schema validation tests
Test stage  /  Integration tests
1m 1s
Test stage / Integration tests
Test stage  /  Acceptance tests
1m 2s
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

4 errors and 8 warnings
Test stage / Unit tests
Process completed with exit code 2.
Test stage / Integration tests
Process completed with exit code 2.
Test stage / Acceptance tests
Process completed with exit code 2.
Test stage / Contract tests
Process completed with exit code 2.
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Commit stage / Check Python format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 / Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/setup-python@v5, test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 Expired
108 KB
sha256:5f49567ec9686441ba6fce0830bfd0eccc5c712ed71656d070137199fdcfa32a
contract-test-results Expired
108 KB
sha256:dfa760589fe66adb16a45d4d398622358c0f8f395de1adc8e14ad3a990a27531
integration-test-results Expired
113 KB
sha256:a230ab3e867a789b059374b1a68676ac0f9828cc72faf2c75d69aa596ffc2a2a
lines-of-code-report.json.zip Expired
859 Bytes
sha256:820e6a0b009cd389931e543815d957b15b468d0284e99205e9669e575bd770f8
sbom-repository-report.json.zip Expired
44.6 KB
sha256:52d80f7639d12645e8e9dc7492ab4abee0d1f122f53adea291ed8c0d82563294
schema-test-results Expired
108 KB
sha256:12192d7fdb9029c116c0cc5170fbf12b26a43e4a14392da39de3d6da17dd6ab6
unit-test-results Expired
185 KB
sha256:02c27e5ec9b0be6f98f4f9a67782e172e0f06dc13b6169482cb9bcc6de4066e3
vulnerabilities-repository-report.json.zip Expired
2.38 KB
sha256:d3679c608503835e6c79921910520d7a39c97c92680f99dacc6421f27fde45e3