Skip to content

CI (main)

CI (main) #5422

Triggered via push April 25, 2026 00:39
Status Failure
Total duration 25m 2s
Artifacts 6

ci.yaml

on: push
Detect Context
4s
Detect Context
Build and Push Image  /  Prepare Build Metadata
14s
Build and Push Image / Prepare Build Metadata
Test and SonarQube  /  Build and Verify Packages
7m 26s
Test and SonarQube / Build and Verify Packages
Matrix: Test and SonarQube / test-python-matrix
Test and SonarQube  /  Validate Dependencies
15s
Test and SonarQube / Validate Dependencies
Test and SonarQube  /  Test UI (Storybook + Unit)
5m 20s
Test and SonarQube / Test UI (Storybook + Unit)
PR Size Check
0s
PR Size Check
Validate Conventional Commit
0s
Validate Conventional Commit
Matrix: Build and Push Image / build-platform
Test and SonarQube  /  SonarQube Analysis
3m 3s
Test and SonarQube / SonarQube Analysis
Build and Push Image  /  Create Multi-Platform Manifest
24s
Build and Push Image / Create Multi-Platform Manifest
Release Readiness  /  Resolve Context
Release Readiness / Resolve Context
Release Readiness  /  ...  /  SCA Scan
Release Readiness / FOSSA Scan / SCA Scan
Release Readiness  /  Prisma Scan
Release Readiness / Prisma Scan
Release Readiness  /  SonarQube Hotspots
Release Readiness / SonarQube Hotspots
Release Readiness  /  Guardian Vulnerability Gate
Release Readiness / Guardian Vulnerability Gate
Release Readiness  /  Release Readiness Status
Release Readiness / Release Readiness Status
RC Gate
0s
RC Gate
Propagate Release Statuses
0s
Propagate Release Statuses
CI Status
4s
CI Status
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 25 warnings
FOSSA Scan / SCA Scan
Process completed with exit code 1.
FOSSA Scan / SCA Scan
Process completed with exit code 2.
FOSSA Scan / SCA Scan
Process completed with exit code 1.
Test and SonarQube / Test Python 3.10
⚠️ Failed to parse file (/home/runner/work/solace-agent-mesh/solace-agent-mesh/junit-3.10.xml) with error Error: Text data outside of root node. Line: 0 Column: 1101825 Char: n
Test and SonarQube / Test Python 3.13
⚠️ Failed to parse file (/home/runner/work/solace-agent-mesh/solace-agent-mesh/junit-3.13.xml) with error Error: Text data outside of root node. Line: 0 Column: 1101826 Char: n
CI Status
Process completed with exit code 1.
CI Status
FOSSA PR Scan is 'failure' (expected: success skipped)
Build and Push Image / Prepare Build Metadata
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, astral-sh/setup-uv@38f3f104447c67c051c4a08e39b64a148898af3a. 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 and Push Image / Prepare Build Metadata
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>0bA3saQAAAAAqKbEo29dkTK/2sgCvT6SLREVOMzAxMDAwMTA2MDM5AEVkZ2U=
Build and Push Image / Prepare Build Metadata
Failed to restore: Cache service responded with 400
Test and SonarQube / Validate Dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
FOSSA Scan / SCA Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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 and Push Image / Build linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@7474bc4690e29a8392af63c5b98e7449536d5c3a, docker/build-push-action@14487ce63c7a62a4a324b0bfb37086795e31c6c1, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2. 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/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L232
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SESSION_SECRET_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Build and Push Image / Build linux/arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@7474bc4690e29a8392af63c5b98e7449536d5c3a, docker/build-push-action@14487ce63c7a62a4a324b0bfb37086795e31c6c1, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2. 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/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L232
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SESSION_SECRET_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Build and Push Image / Create Multi-Platform Manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@7474bc4690e29a8392af63c5b98e7449536d5c3a, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2. 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 and SonarQube / Test UI (Storybook + Unit)
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/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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 and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/pages/TaskExecutionHistoryPage.tsx#L51
The 'executions' logical expression could make the dependencies of useEffect Hook (at line 66) change on every render. To fix this, wrap the initialization of 'executions' in its own useMemo() Hook
Test and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/pages/ArtifactsPage.tsx#L374
React Hook useEffect has a missing dependency: 'artifact'. Either include it or remove the dependency array
Test and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/models/ModelEditPage.tsx#L58
React Hook useCallback has a missing dependency: 'agentsRefetch'. Either include it or remove the dependency array
Test and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/chat/file/FileMessage.tsx#L29
The 'artifacts' conditional could make the dependencies of useMemo Hook (at line 33) change on every render. Move it inside the useMemo callback. Alternatively, wrap the initialization of 'artifacts' in its own useMemo() Hook
Test and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/chat/file/FileIcon.tsx#L180
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
Test and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/chat/file/FileIcon.tsx#L46
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
Test and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/chat/file/FileIcon.tsx#L23
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
Test and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/chat/file/DocumentThumbnail.tsx#L91
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
Test and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/chat/file/ArtifactMessage.tsx#L175
React Hook useCallback has a missing dependency: 'props'. Either include it or remove the dependency array. However, 'props' will change when *any* prop changes, so the preferred fix is to destructure the 'props' object outside of the useCallback call and refer to those specific props inside useCallback
Test and SonarQube / Test UI (Storybook + Unit): client/webui/frontend/src/lib/components/chat/UserAvatar.tsx#L14
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
Test and SonarQube / Build and Verify Packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-python@8d9ed9ac5c53483de85588cdf95a591a75ab9f55, astral-sh/setup-uv@38f3f104447c67c051c4a08e39b64a148898af3a. 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 and SonarQube / Test Python 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/setup-python@8d9ed9ac5c53483de85588cdf95a591a75ab9f55, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, mikepenz/action-junit-report@3585e9575db828022551b4231f165eb59a0e74e3. 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 and SonarQube / Test Python 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/setup-python@8d9ed9ac5c53483de85588cdf95a591a75ab9f55, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, mikepenz/action-junit-report@3585e9575db828022551b4231f165eb59a0e74e3. 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 and SonarQube / SonarQube Analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, sonarsource/sonarqube-scan-action@fd88b7d7ccbaefd23d8f36f73b59db7a3d246602. 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
SolaceLabs~solace-agent-mesh~DHJXV1.dockerbuild
115 KB
sha256:233c3e61b4edb741aaddebf0eddea991f217f0e53f67e49852147adc71bea288
SolaceLabs~solace-agent-mesh~KGGIJ2.dockerbuild
115 KB
sha256:7af964bdfb81aaa92e01cf284523605ebdb2e4089c3bbde282a6fc1267e09106
dependency-conflict-report
1.02 KB
sha256:2e61c4be8cbd7c41625bdf2cdfe640aaf83041d21155a723e9f23cbc4e33da10
python-coverage-3.10 Expired
356 KB
sha256:d3cea24a82af98be440574686d7d68589e584172e87e1a9c7cadbd1cf464cadc
python-coverage-3.13 Expired
355 KB
sha256:d4688c62f3c30f905dee7a58a7a3bccd0da58462d519c690e7104970dcc41563
ui-coverage Expired
3.25 MB
sha256:0d5fe73ef2b663dcc6c634ebed3516ddd8372f70634a88f15b174caa6398e4d0