Skip to main content

TestVibe 0.4.1

All release notes · Self-hosted upgrade guide

Archived release. Superseded by 0.4.5. Downloads are no longer offered; these notes remain available for upgrade planning.

An appliance fix. Replace the VHDX or OVA if you downloaded one before 6 August 2026.

The virtual appliance shipped with a network configuration that named one specific adapter — the one present on the machine that built it. On any other hypervisor the adapter is presented under a different name, nothing matched it, and the appliance booted with no IP address, no first-boot banner, and no way to sign in. It affected Hyper-V, VMware and VirtualBox alike; the symptom looked like a broken image rather than a configuration problem, because it was one.

The image now configures whatever adapter it is given. Our own build-time boot test was part of the failure — it booted the appliance on the same adapter it was built with, so it could never have caught this — and it now tests on a different one.

Docker and Kubernetes installs were never affected.

  • Helm charts refuse to over-scale. runner.replicaCount and browser.replicaCount above 1 now stop the install with an explanation. Run state lives in the process that took the job, and the app polls for it through a load-balanced Service, so a second replica did not share load — it lost runs. See Capacity and scaling.
  • Everything in 0.4.0 below is unchanged.

Upgrading the appliance: attach the new OS disk and keep your existing data disk. Your database, artifacts, install identity and license all live on disk 2. Do not discard it.

Schema migrations: this release applies V0266 and V0267 on first start. They run automatically and are one-way — take a database backup first, as you should for any upgrade.