Skip to content
Docker Security Scan

chore(testing): make ContextForge benchmarks reproducible and CI-friendly #6007

Sign in to view logs

chore(testing): make ContextForge benchmarks reproducible and CI-friendly

chore(testing): make ContextForge benchmarks reproducible and CI-friendly #6007

Triggered via pull request April 16, 2026 14:43
@lucarliglucarlig
synchronize #3680
chore/build-prod-image-with-profilers
Status Success
Total duration 1h 10m 31s
Artifacts 6

docker-scan.yml

on: pull_request
Security Scan
3m 58s
Security Scan
Rust-enabled container smoke
11m 36s
Rust-enabled container smoke
Matrix: container-smoke
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Security Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
Security Scan
Retention days cannot be greater than the maximum allowed retention set within the repository. Using 10 instead.
Container Smoke (a2a-echo-agent)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
Container Smoke (python-sandbox)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
Container Smoke (main)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
Rust-enabled container smoke
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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
IBM~mcp-context-forge~3M6AVW.dockerbuild
64.5 KB
sha256:d7178b88c9426a582fd289146d1381a671747a3f9d7be8bfbfdfb58d974d8c5b
IBM~mcp-context-forge~A6PS8X.dockerbuild
134 KB
sha256:41b9cc9446aada6b724253ddfed3c2fe42d5f082e185536f354c7ce1045d269f
IBM~mcp-context-forge~BNP69Q.dockerbuild
111 KB
sha256:75912e2cdb838c50e22177d868e238dd1e1d7e0fcb49ae505d73d1f82ef79e45
IBM~mcp-context-forge~NNER67.dockerbuild
40.5 KB
sha256:4ad723c5eb8ff65cd5559717d1b5c929c72dd7127d93dbe1674e8257b35f71e6
IBM~mcp-context-forge~YF0B9N.dockerbuild
37.1 KB
sha256:13f611aff0f623b611d3e4bc94b4f0e778ea248fb1a7848c6e47fccc7ce42eca
sbom
514 KB
sha256:e1e8ff7d6d636e9a9b7e60186f7b8b200a99355c8e53927ab492cdbbdc3fc883