Skip to main content

Upgrade and maintain TestVibe

Back up first, keep your persistent data and keys, and apply migrations before the new application starts.

Upgrade an appliance​

  • Read the release notes for your installed and target versions. Shut down cleanly and back up both disks before replacing anything.
  • Replace the OS disk with the new release and retain your existing data disk. Never attach the empty data disk from a new import alongside your retained data disk.
  • Boot and allow migrations to finish. Verify application sign-in, an existing project, a test run, and artifact access.
  • When moving to 0.4.14 or later, use the physical recovery menu to list users and grant instance administration to your chosen existing account. Sign in normally and open Settings → Administration.
  • Do not roll older code back over a migrated database without checking compatibility. A full rollback restores the matching database/data snapshot and OS version.

Upgrade containers or Kubernetes​

  • Download the new Compose bundle and replace docker-compose.yml with its version-pinned file. Preserve .env and persistent volumes; compare the new .env.example for additions.
  • Run docker compose pull, docker compose up -d migrate, then docker compose up -d --remove-orphans. This removes the retired admin container without deleting persistent volumes.
  • For Kubernetes, upgrade to the target chart using your saved values and secrets. Wait for the migration job and application readiness. The chart removes the separate admin workload.
  • For an existing account, run the recovery tool users command, then grant USER_ID. Keep the same database and encryption-key configuration. See Troubleshooting → Host recovery.
# First replace docker-compose.yml with the new release’s file.
docker compose pull
docker compose up -d migrate
docker compose up -d --remove-orphans

OS and service maintenance​

  • The appliance configures operating-system security updates. Schedule host maintenance and VM restarts according to your organization’s policy.
  • Application releases are installed separately; checking for an update in Administration does not install it.
  • Verify the application, runners and artifact access after maintenance. Preserve both disks and your backup history.