Skip to content

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

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

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

Triggered via pull request March 12, 2026 08:12
Status Failure
Total duration 7m 47s
Artifacts 6

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
6s
Set CI/CD metadata
Commit stage  /  Scan secrets
8s
Commit stage / Scan secrets
Commit stage  /  Check file format
9s
Commit stage / Check file format
Commit stage  /  Check Python format
6s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
4s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
11s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
17s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
10s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
42s
Commit stage / Scan dependencies
Test stage  /  Unit tests
3m 9s
Test stage / Unit tests
Test stage  /  Contract tests
3m 37s
Test stage / Contract tests
Test stage  /  Schema tests
3m 16s
Test stage / Schema tests
Test stage  /  Integration tests
3m 25s
Test stage / Integration tests
Test stage  /  Create coverage artefact name
3s
Test stage / Create coverage artefact name
Test stage  /  Merge test coverage
3m 10s
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 9 warnings
Test stage / Schema tests
ENOENT: no such file or directory, open 'gateway-api/test-artefacts/schema-tests.xml'
Test stage / Schema tests
Process completed with exit code 2.
Test stage / Merge test coverage
Provided artifact name input during validation is empty
Test stage / Merge test coverage
Unable to download artifact(s): Artifact not found for name: schema-test-results Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
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 / 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 / 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 / Schema 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 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: 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 / Merge test coverage
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/

Artifacts

Produced during runtime
Name Size Digest
contract-test-results Expired
107 KB
sha256:cf3333bb11f7c060b3fd0a96882b0731ab7640800149e6369593456cd972186e
integration-test-results Expired
108 KB
sha256:d2f0b3758d918598da181599feb013e6d422b930ebfde81d24c5b0c0a83ac50e
lines-of-code-report.json.zip Expired
865 Bytes
sha256:f93c91ac2475c015a78125c92b650a54c685ec9385150e176d49e8523bbd40ea
sbom-repository-report.json.zip Expired
45.2 KB
sha256:50659af61b3fac4f301010b19fcebf52d9cb30ddcd997f5f11e790aefea2aa66
unit-test-results Expired
183 KB
sha256:e92c6b38f14f0fa54fd5ff02f83453a04e3a192141507ef87b739d546acd19a3
vulnerabilities-repository-report.json.zip Expired
2.37 KB
sha256:c794e393e0632ec812db5bd5a05462fb17acf7027607aeda64c0ae3408f049f6