Skip to content

CCM-15100: Changing Results Bucket Config #1700

CCM-15100: Changing Results Bucket Config

CCM-15100: Changing Results Bucket Config #1700

Triggered via pull request March 26, 2026 12:30
Status Success
Total duration 2m 13s
Artifacts 4

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
6s
Set CI/CD metadata
Commit stage  /  Scan secrets
7s
Commit stage / Scan secrets
Commit stage  /  Check file format
8s
Commit stage / Check file format
Commit stage  /  Check Markdown format
5s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
10s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
4s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
11s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
42s
Commit stage / Scan dependencies
Commit stage  /  Detect Terraform Changes
6s
Commit stage / Detect Terraform Changes
Commit stage  /  Run terraform-docs
9s
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
23s
Commit stage / Lint Terraform
Test stage  /  Linting
5s
Test stage / Linting
Test stage  /  Unit tests
6s
Test stage / Unit tests
Test stage  /  Test coverage
4s
Test stage / Test coverage
Test stage  /  Perform static analysis
3s
Test stage / Perform static analysis
Build stage  /  Build Docs
39s
Build stage / Build Docs
Build stage  /  Artefact 1
5s
Build stage / Artefact 1
Build stage  /  Artefact n
5s
Build stage / Artefact n
Acceptance stage  /  Environment set up
4s
Acceptance stage / Environment set up
Acceptance stage  /  Contract test
4s
Acceptance stage / Contract test
Acceptance stage  /  Security test
4s
Acceptance stage / Security test
Acceptance stage  /  UI test
5s
Acceptance stage / UI test
Acceptance stage  /  UI performance test
6s
Acceptance stage / UI performance test
Acceptance stage  /  Integration test
6s
Acceptance stage / Integration test
Acceptance stage  /  Accessibility test
4s
Acceptance stage / Accessibility test
Acceptance stage  /  Load test
5s
Acceptance stage / Load test
Acceptance stage  /  Environment tear down
3s
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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 / 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. 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 / Build Docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/configure-pages@v5, actions/setup-node@v4, actions/upload-artifact@v4, ruby/setup-ruby@v1.180.1. 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/
Build stage / Build Docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0SifFaQAAAAAMof58whBSSaYKY2fOqvltUEhMMzBFREdFMDIxNQBFZGdl
Build stage / Build Docs
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
jekyll-docs-0.0.2-20260326.123030+8bc21ca Expired
366 KB
sha256:5876f7916635115947331f0fb34419649bfb7390c2dce53161050452a3e06234
lines-of-code-report.json.zip Expired
883 Bytes
sha256:aab51e788ecd37fe4734d39686c2eca481dfd60a5e6988189b85f5491c33ce55
sbom-repository-report.json.zip Expired
13.7 KB
sha256:3086f6c4f1ae97980527ecff07eb4aa7f5e9bbc17351a8057513f7efdc7a2770
vulnerabilities-repository-report.json.zip Expired
4.8 KB
sha256:a5991035c097bae50af9d2e7e8b16bdeda6d9f0f277d96efa6dbac9cb2308110