Skip to content

[GPCAPIM-397] Set up INT test provider requests #2928

[GPCAPIM-397] Set up INT test provider requests

[GPCAPIM-397] Set up INT test provider requests #2928

Triggered via pull request April 27, 2026 22:57
Status Success
Total duration 4m 58s
Artifacts 9

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
4s
Set CI/CD metadata
Commit stage  /  Scan secrets
6s
Commit stage / Scan secrets
Commit stage  /  Check file format
7s
Commit stage / Check file format
Commit stage  /  Check Python format
9s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
12s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
9s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
24s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
9s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
49s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
4s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
45s
Test stage / Unit tests
Test stage  /  Contract tests
1m 12s
Test stage / Contract tests
Test stage  /  Schema validation tests
1m 38s
Test stage / Schema validation tests
Test stage  /  Integration tests
1m 4s
Test stage / Integration tests
Test stage  /  Acceptance tests
1m 19s
Test stage / Acceptance tests
Test stage  /  Merge test coverage
37s
Test stage / Merge test coverage
Test stage  /  SonarCloud Analysis
1m 7s
Test stage / SonarCloud Analysis
Build stage  /  Artefact 1
5s
Build stage / Artefact 1
Build stage  /  Artefact 2
4s
Build stage / Artefact 2
Acceptance stage  /  Environment set up
6s
Acceptance stage / Environment set up
Acceptance stage  /  Security test
5s
Acceptance stage / Security test
Acceptance stage  /  UI test
4s
Acceptance stage / UI test
Acceptance stage  /  UI performance test
5s
Acceptance stage / UI performance test
Acceptance stage  /  Load test
3s
Acceptance stage / Load test
Acceptance stage  /  Environment tear down
4s
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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 / 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 / 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 / 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:912930c42deb9f1dec1b25d8a35e007c0dd3684310b8f1dad35d15077b2c9a35
contract-test-results
117 KB
sha256:f714504bb0764287855a64fa6e70ef24fa7c990fa13f2aae50e9ff88fc312578
coverage-feature-GPCAPIM-397-set-up-int-test-provider-requests-2928
795 KB
sha256:be15f5a3f22c5450af16215f661d6a537df54d27863fb417b3d7d880bcf627ff
integration-test-results
114 KB
sha256:77a45ff537357657ba758643de218695bd961ed7a9b0f680b1ba1622b0c1b5c4
lines-of-code-report.json.zip
865 Bytes
sha256:d8a172cd203100c8937f3ead1e67eea6b05207eb75d45f1e41f5b7ef243d276a
sbom-repository-report.json.zip
96.9 KB
sha256:b38622a2555759ef227aea84a62a760d221bacaeebf6a1d62b32846739ceae8b
schema-test-results
114 KB
sha256:fbaf6f5ef8b8e6c37bdb541b5e724e8cd85df14059fcfd17a0021415461304af
unit-test-results
236 KB
sha256:56765ffcaedbf2883f9c59577b3430bfd65a04a7ee71a844709a6053b13b2491
vulnerabilities-repository-report.json.zip
4.01 KB
sha256:b952e806f9b5c4ecf5563aa302c31b52d67bcafacc5cb6b119a5ef180f3e52fe