Skip to content

[ELI-619] - cache campaign configs unless we send a reserved consumer id #3269

[ELI-619] - cache campaign configs unless we send a reserved consumer id

[ELI-619] - cache campaign configs unless we send a reserved consumer id #3269

Triggered via pull request March 20, 2026 11:14
Status Failure
Total duration 2m 48s
Artifacts 4

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
9s
Commit stage / Scan secrets
Commit stage  /  Check file format
9s
Commit stage / Check file format
Commit stage  /  Check Markdown format
4s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
8s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
6s
Commit stage / Lint Terraform
Commit stage  /  Checkov Terraform
31s
Commit stage / Checkov Terraform
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
40s
Commit stage / Scan dependencies
Commit stage  /  OWASP Dependency Scan
33s
Commit stage / OWASP Dependency Scan
Commit stage  /  Check for dead code
32s
Commit stage / Check for dead code
Test stage  /  Linting
38s
Test stage / Linting
Test stage  /  Unit tests
56s
Test stage / Unit tests
Test stage  /  Perform static analysis
56s
Test stage / Perform static analysis
Build stage  /  Lambda Artefact
Build stage / Lambda Artefact
Acceptance stage  /  Environment set up
Acceptance stage / Environment set up
Acceptance stage  /  Accessibility test
Acceptance stage / Accessibility test
Acceptance stage  /  Contract test
Acceptance stage / Contract test
Acceptance stage  /  Integration test
Acceptance stage / Integration test
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

1 error and 4 warnings
Test stage / Linting
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 / OWASP Dependency Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: github/codeql-action/upload-sarif@v3. 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 / OWASP Dependency Scan
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
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/

Artifacts

Produced during runtime
Name Size Digest
coverage.xml
7.18 KB
sha256:177cc8bb1777831fe989625388c31afffea71aad49c377a5e6ec35241ca7d096
lines-of-code-report-.json.zip Expired
844 Bytes
sha256:bfb45fdff7173f5c93fe71ecf616ae4a842477ad0e25aa3f548fd6a7e1f6fa94
sbom-repository-report.json.zip Expired
58.8 KB
sha256:171520e6424d411587956e0e52d04322b61be649f719900c1e7c0af2ac58d9a4
vulnerabilities-repository-report-.json.zip Expired
4.47 KB
sha256:0e3c9103ad9bfd2bad446fada5c887ebc2b25d2413faa93b9ec6a8c9fe08d3ab