CI Integration

vHaaS integrates hardware assemblies into CI pipelines, so tests run against real hardware as a normal pipeline step.

• Basic CI Integration — set up your first job on the vHaaS GitLab runner.
• Advanced CI Integration — choose assemblies at run time, test on several assemblies in parallel, and book assemblies through the API.
• Self-hosted GitLab Runner — run the custom executor in your own environment.

For the variables and job environment the runner provides, see the CI reference.

How the runner works

A job tagged vHaaS is picked up by the vHaaS runner, which then:

1. Books an assembly — it reads ASSEMBLY_REF, SESSION_DURATION and SESSION_TIMEOUT and waits until an assembly becomes available (up to SESSION_TIMEOUT). With a comma-separated ASSEMBLY_REF, the first available assembly is used.
2. Connects to the assembly's default GitLab-runner VM over a secured per-job tunnel, so no direct network route to the VM is required.
3. Runs the job script on that VM, with hardware access.
4. Releases the assembly when the job ends — including on failure or cancellation.