Skip to content

CCM-16439: Bucket Expiry Policies #2639

CCM-16439: Bucket Expiry Policies

CCM-16439: Bucket Expiry Policies #2639

Triggered via pull request April 27, 2026 14:42
Status Failure
Total duration 18m 6s
Artifacts 7

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
8s
Set CI/CD metadata
Commit stage  /  Scan secrets
16s
Commit stage / Scan secrets
Commit stage  /  Check file format
7s
Commit stage / Check file format
Commit stage  /  Check Markdown format
9s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
8s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
5s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
9s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
1m 0s
Commit stage / Scan dependencies
Commit stage  /  Detect Terraform Changes
6s
Commit stage / Detect Terraform Changes
Commit stage  /  Run terraform-docs
12s
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
21s
Commit stage / Lint Terraform
Test stage  /  Contract tests
48s
Test stage / Contract tests
Test stage  /  Linting
3m 0s
Test stage / Linting
Test stage  /  Typecheck
2m 8s
Test stage / Typecheck
Test stage  /  Detect Schema Changes
8s
Test stage / Detect Schema Changes
Test stage  /  Unit tests
3m 28s
Test stage / Unit tests
Test stage  /  Check generated dependencies
0s
Test stage / Check generated dependencies
Test stage  /  Perform static analysis
1m 40s
Test stage / Perform static analysis
Build stage  /  Detect Documentation Changes
8s
Build stage / Detect Documentation Changes
Build stage  /  Build Docs
Build stage / Build Docs
Trigger dynamic environment creation
11m 18s
Trigger dynamic environment creation
Publish stage  /  Publish packages
Publish stage / Publish packages
Acceptance stage  /  Accessibility test
Acceptance stage / Accessibility 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
Fit to window
Zoom out
Zoom in

Annotations

1 error and 15 warnings
Trigger dynamic environment creation
Process completed with exit code 1.
Test stage / Detect Schema Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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 / Linting: src/typescript-schema-generator/src/generate-types.ts#L34
Found writeFileSync from package "node:fs" with non literal argument at index 0
Test stage / Linting: src/typescript-schema-generator/src/generate-guard-functions.ts#L51
Found writeFileSync from package "node:fs" with non literal argument at index 0
Test stage / Linting: lambdas/print-analyser/src/__tests__/test-data.ts#L61
Found readFileSync from package "node:fs" with non literal argument at index 0
Test stage / Linting: utils/utils/src/event-publisher/event-publisher.ts#L101
Function Call Object Injection Sink
Test stage / Linting: utils/utils/src/dynamodb/delete-dynamo-batch.ts#L47
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/dynamodb/delete-dynamo-batch.ts#L34
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/config-reader.ts#L69
Variable Assigned to Object Injection Sink
Test stage / Linting: utils/utils/src/cache/cache.ts#L52
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/cache/cache.ts#L33
Variable Assigned to Object Injection Sink
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/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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 / Perform static analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@634f93cb2916e3fdff6788551b99b062d0335ce0. 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/
Build stage / Detect Documentation Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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
code-coverage-report
17.1 KB
sha256:edca0ab11f4104b47ca9bae912c9813ab21585f4ad66c9fd8f78a88e555f243a
lines-of-code-report.json.zip
966 Bytes
sha256:8c7d770e9085eafa34bc240f0fd693d9891f4f88d128ef1715ed355858cfe3e6
pact-contracts
609 Bytes
sha256:2460c76208a62070d2bbcb1f860308c7d16901cd449f126bce47f076588b6a63
python-coverage-reports
13.4 KB
sha256:f756ccfc35cb07cd3db517eeb4e8e74eccdd5925d6fcdb5fa16164fcb4e55e83
sbom-repository-report.json.zip
377 KB
sha256:b59ec30a47128fc37f60a7001c7e5aeaf15126714011e76ba4259e9b05af4279
unit-tests
1.97 MB
sha256:02a69332e8f36d4a8a3518d227be11f848ad98aea08cc7cc2227e0a221084e8f
vulnerabilities-repository-report.json.zip
4.43 KB
sha256:f37dd3200a44896c631936876a14349116059e87a3121f365785b7d1ae1281d8