Skip to content

ci: Install the monitors from monitors-build releases - #1183

Draft
cmainas wants to merge 1 commit into
mainfrom
ci/use_monitors-build
Draft

cmainas wants to merge 1 commit into
mainfrom
ci/use_monitors-build

Conversation

@cmainas

@cmainas cmainas commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Description

The e2e tests gathered the monitors from several places: QEMU came from apt, Firecracker and Cloud Hypervisor from their upstream releases, virtiofsd from an S3 bucket, and Solo5 was built from source.

To resolve that, we created monitors-build repository which publishes static builds of all of them, bundled in a single archive per architecture. Therefore, use these archives instead.

The workflows still set the version of each monitor, and a new find-monitors-release action looks up the monitors-build release that bundles exactly those versions. The archive extracts to /opt/urunc, and the urunc configuration points every monitor there.

On pull requests, vm_test checks out the base branch, so it fetches the action from the commit that the workflow itself was loaded from.

Since no monitors-build release provides Solo5 v0.9.3, the default Solo5 version moves to v0.12.1.

Related issues

How was this tested?

In the PR CI.

LLM usage

Opus 5.5

Checklist

  • I have read the contribution guide.
  • The linter passes locally (make lint).
  • The e2e tests of at least one tool pass locally (make test_ctr, make test_nerdctl, make test_docker, make test_crictl).
  • If LLMs were used: I have read the llm policy.

The e2e tests gathered the monitors from several places: QEMU came
from apt, Firecracker and Cloud Hypervisor from their upstream
releases, virtiofsd from an S3 bucket, and Solo5 was built from
source.

To resolve that, we created monitors-build repository which publishes
static builds of all of them, bundled in a single archive per
architecture. Therefore, use these archives instead.

The workflows still set the version of each monitor, and a new
find-monitors-release action looks up the monitors-build release that
bundles exactly those versions.  The archive extracts to `/opt/urunc`,
and the urunc configuration points every monitor there.

On pull requests, vm_test checks out the base branch, so it fetches
the action from the commit that the workflow itself was loaded from.

Since no monitors-build release provides Solo5 v0.9.3, the default
Solo5 version moves to v0.12.1.

Signed-off-by: Charalampos Mainas <charalampos.mainas@gmail.com>
@netlify

netlify Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for urunc canceled.

Name Link
🔨 Latest commit e8e0b14
🔍 Latest deploy log https://app.netlify.com/projects/urunc/deploys/6ae3965ce6b921672eba2fb3

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Replace the manually installed monitor binaries with getting them from monitors-build

1 participant