Skip to content

backmesh v0.2.0

Choose a tag to compare

@depombo depombo released this 07 Nov 15:50

Action required: uninstall, then install again

This release keeps no compatibility with 0.1.x installations. Run backmesh uninstall with your current release, then backmesh install with this one. What changed:

  • One backmesh GitHub App. backmesh no longer creates a private GitHub App in your org. An org owner installs the public backmesh App with one click during backmesh install. The App's private key stays with backmesh and never enters your accounts. Your listener gets hour-long tokens for your own org from api.backmesh.com.
  • User-namespace runner pools. Runners no longer run privileged. Each runner pool is a user-namespace pool, so a job is no longer root on its VM.

Your cloud credentials, code, secrets, caches, logs and runners stay in your accounts.

Changes

  • One-click App install. install signs in an org admin with a device code, prints the App's install link until an org owner installs it, and only then creates anything billed. upgrade --app-key and the App key-age warning are gone, because there's no App key in your accounts to rotate.
  • Several orgs on one control plane. backmesh install --org <second> against an existing installation adds that org's listener and shares the runner pools and the 500-runner cap with the other orgs, first come, first served. Every org must have the same owner, confirmed at the prompt or with --same-owner. status shows each org, upgrade updates every org, and uninstall --org removes one org.
  • One uninstall path. backmesh uninstall always does the same thing, and --yes skips its confirmations:
    1. For each org, it signs in an org admin with a device code, which CI can enter from the job log. It refuses while another backmesh installation in the org has used the App in the last hour.
    2. It stops the org's listener and removes backmesh's runners, scale sets and runner group from GitHub.
    3. It removes the App from the org, unless another backmesh installation there has used it in the last hour.
    4. Once no org is left on the control plane, it deletes the cloud side if the control plane still answers. If the control plane is gone, it says so and lists what may be left.
  • Retry on demand after a spot reclaim. Each cloud gets an on-demand pool that idles at zero VMs. When a spot VM is reclaimed, backmesh reruns the run's failed jobs on demand once the run finishes, if only reclaims failed it, up to twice per run. A breaker pauses spot on a pool after repeated reclaims. To keep a job's reclaim from rerunning its run, add backmesh-noretry to its runs-on. New backmesh-od-<n> labels (backmesh-<cloud>-od-<n> with several clouds) always run on demand.
  • Runner pools idle at zero VMs. Spot and on-demand runner pools scale to zero VMs when no jobs run, so an idle installation pays only for its control plane: about $86 a month on AWS, $74 on GCP and $111 on Azure. The first job after an idle gap waits a few minutes for a VM to start.
  • backmesh logs. Shows the listener's log, or one runner's log by its runner name.
  • Self-contained CLI. You install only backmesh. It fetches and checks the anycloud release it pins and handles the GitHub sign-in itself, and its messages no longer ask you to run anycloud commands.
  • Plans. Starter (50,000 jobs per rolling 30 days, $40 a month or $350 a year), Growth (200,000; $125 or $1,050), Scale (500,000; $250 or $2,100) and Unlimited ($500 or $4,200), each with a 15-day free trial. Subscriptions open soon. Going over a tier only warns, and jobs never stop over billing. Non-commercial use (open source, non-profits, education, personal projects) is free once an org admin declares it on the billing page, with a public link back to backmesh.com.
  • Revoke an install key. On the billing page, any admin of the key's org can revoke the key. This is separate from disowning an install, which only stops counting its jobs.

Images, signed with cosign keyless by this repository's workflows:

  • runner: ghcr.io/anycloud-sh/backmesh-runner@sha256:0cd79deaa0f23dd1a5a8b0ca84f51e6e4e88c6c62b1d60a1c96c0d5c43b6618c
  • listener: ghcr.io/anycloud-sh/backmesh-listener@sha256:c99a18407818e850c997869a3f054fa4f52f700ad286fdffe97ba1c7632a862f

Verify each with:

cosign verify ghcr.io/anycloud-sh/backmesh-runner@sha256:0cd79deaa0f23dd1a5a8b0ca84f51e6e4e88c6c62b1d60a1c96c0d5c43b6618c --certificate-identity https://github.com/anycloud-sh/backmesh/.github/workflows/image.yml@refs/tags/v0.2.0 --certificate-oidc-issuer https://token.actions.githubusercontent.com
cosign verify ghcr.io/anycloud-sh/backmesh-listener@sha256:c99a18407818e850c997869a3f054fa4f52f700ad286fdffe97ba1c7632a862f --certificate-identity https://github.com/anycloud-sh/backmesh/.github/workflows/image.yml@refs/tags/v0.2.0 --certificate-oidc-issuer https://token.actions.githubusercontent.com

Pins anycloud 0.1.73; each CLI binary embeds compatibility.json, which backmesh upgrade reads. checksums.txt holds their sha256 digests.