[GPCAPIM-289]-[Pass integration tests through APIM proxy (with mock CIS2)]-[RP] #1672
BJSS-russell-pollockcicd-1-pull-request.yaml
on: pull_request
Set CI/CD metadata
9s
Commit stage
/
Scan secrets
12s
Commit stage
/
Check file format
15s
Commit stage
/
Check Python format
10s
Commit stage
/
Check Markdown format
7s
Commit stage
/
Check English usage
12s
Commit stage
/
Lint Terraform
42s
Commit stage
/
Count lines of code
8s
Commit stage
/
Scan dependencies
54s
Test stage
/
Unit tests
43s
Test stage
/
Contract tests
1m 27s
Test stage
/
Schema validation tests
1m 34s
Test stage
/
Integration tests
1m 31s
Test stage
/
Acceptance tests
1m 59s
Acceptance stage
/
Load test
Acceptance stage
/
Security test
Acceptance stage
/
UI performance test
Acceptance stage
/
UI test
Acceptance stage
/
Environment tear down
Annotations
8 errors and 12 warnings
|
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 / 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 / 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 / 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.
|
|
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 / 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 / Contract 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 / Integration 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: 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
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: 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
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
Expired
|
864 Bytes |
sha256:6595d97cfe575c03e9d98c5a4cef8e81b4b06af730cf9b06b3cfb9db7a27e3a2
|
|
|
sbom-repository-report.json.zip
Expired
|
44.6 KB |
sha256:4c37db434d6162bbe37ece2a145de1cf2ce4f90bf23d8137600f962c23bab637
|
|
|
unit-test-results
Expired
|
183 KB |
sha256:31cf65216009499ba9f28e66db25658af1598694169b09737d787ed3a94c51b5
|
|
|
vulnerabilities-repository-report.json.zip
Expired
|
2.38 KB |
sha256:a47debdfa66252870b9fe1b2a59fa16ad1f920c9eef1eabb1404cee42ad151bd
|
|