Skip to content

[GPCAPIM-419]-[Required Missing Header Not Rejected (Content-Type)]-[RP] #2997

[GPCAPIM-419]-[Required Missing Header Not Rejected (Content-Type)]-[RP]

[GPCAPIM-419]-[Required Missing Header Not Rejected (Content-Type)]-[RP] #2997

Triggered via pull request April 30, 2026 09:58
Status Failure
Total duration 2m 39s
Artifacts 7

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
7s
Commit stage / Check file format
Commit stage  /  Check Python format
8s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
6s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
13s
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  /  Create coverage artefact name
5s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
49s
Test stage / Unit tests
Test stage  /  Contract tests
1m 34s
Test stage / Contract tests
Test stage  /  Schema validation tests
1m 32s
Test stage / Schema validation tests
Test stage  /  Integration tests
1m 6s
Test stage / Integration tests
Test stage  /  Acceptance tests
1m 8s
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

3 errors and 6 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 / 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 / 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/
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.

Artifacts

Produced during runtime
Name Size Digest
acceptance-test-results
113 KB
sha256:8a9645acf17cafd1f88838fc1d6860be83eb2316e117300197ef4db1706f728a
integration-test-results
114 KB
sha256:40068575f15799341acbbcb1e1a5f9bd1841068cecdf24b4c9977e395523e9ca
lines-of-code-report.json.zip
859 Bytes
sha256:c717cebfd30d82d826e846a164eb4e73b4f075db98d298f51f8dce9e8d9ef950
sbom-repository-report.json.zip
96.3 KB
sha256:94ea31e66b056e394734749aeb3d2eff865498b56b8b28ec6074fa47e9623f80
schema-test-results
116 KB
sha256:15784d39be860f5252519f618c4fcbedf5fd37ae9776601aa8e1a08834fa80a5
unit-test-results
233 KB
sha256:a910fcac397b5abfa70a77a92e304e3ad221ed3b36c724400633d64741598f9b
vulnerabilities-repository-report.json.zip
4.02 KB
sha256:f1db73942660cee0cebca90512481abff9198473f3fae4fb73a6843e2057a233