Repository navigation
backmesh v0.3.0
Reinstall required: run backmesh uninstall with your current release, then backmesh install with this one. backmesh upgrade refuses installations from before v0.3.0.
Changes
- Each job gets its own VM. Every GitHub Actions job runs on a fresh spot or on-demand VM in your cloud account, deleted when the job ends. Nothing is shared between jobs, so there are no pools to size or isolate.
- Runners in several regions. Choose where things run with
--control-plane <cloud>:<region>and--runners <cloud>[:<region>,...], on AWS, GCP and Azure. Azure runners aren't yet proven on our own CI; that proof follows in a patch release. A bare--runners awsuses that cloud's default regions, such as AWS'sus-regions near a US control plane;--runners aws:us-east-2,us-west-2keeps jobs in exactly those. Each job's VM launches in the cheapest region with room and tries another when the cloud refuses for capacity or quota. Labels stay the same. - Slow starts move. A spot runner whose launches the cloud keeps refusing gets a replacement in another runner region after 3 minutes. A region whose quota can't fit one runner is skipped until you raise it, and
backmesh statusnames the quota. - Runners start ahead of your jobs. backmesh learns each workflow's shape from its past runs, inside your account, and starts runners shortly before later jobs queue, so most of them don't wait for a VM. Unused runners are removed after 60 seconds.
backmesh cue --in <seconds>. When you, or your coding agent, start the checks you run before a push, runbackmesh cue --in 120with the seconds until you expect to push, 30 to 600, and the run's first jobs find runners waiting.backmesh cue --canceldrops it. The repo and branch are encrypted to your listener; backmesh.com sees only your org, your GitHub user and the time. If backmesh.com is down, CI starts cold and nothing fails.- Sign in with a connect link.
install,upgradeandrotate-keyprint ahttps://backmesh.com/connect/<code>link to open on any device and sign in with GitHub. During install, the org owner installs the backmesh App on the same page.--deviceuses a GitHub device code instead. - See the plan first.
backmesh install --planandbackmesh upgrade --planprint what would change and what it costs, and a plan ID;--yes --plan-id <id>applies exactly that plan without a terminal. - Paid plans with a 15-day trial. Every plan starts with a 15-day free trial; checkout takes a card, charged on day 16 unless you cancel. There's no free tier, and the free non-commercial use is gone.
upgradeis blocked while an org has no plan or an unpaid bill; jobs never stop over billing. backmesh rotate-key --org <org>. Replaces an org's install key: it signs in an org admin, gives the listener a new key and only then revokes the old one. The billing page no longer lists or revokes install keys.- Docker and KVM without privileged mode. Jobs use their VM's own Docker, so a port a job's container publishes is on
localhost, as on GitHub's runners.backmesh-kvm-*labels give/dev/kvmon AWS, GCP and Azure. - No Docker or saved cloud keys to install.
backmesh installuses your signed-inaws,gcloudorazCLI, and connects each cloud with a keyless role.upgradeandstatusneed no cloud CLI. - A fresh runner group per install, so a reinstall never reuses a deleted group's name.
- Telemetry now includes each runner's VM type and boot time. The telemetry page lists every field.
Images, signed with cosign keyless by this repository's workflows:
- runner:
ghcr.io/anycloud-sh/backmesh-runner@sha256:a3642da07f8991fb73bd8995af449dffe126cfb042e13d9c8005b0749dd4d703 - listener:
ghcr.io/anycloud-sh/backmesh-listener@sha256:301d1545631cf018c97d9bc8730a14de31cd13e5dff1311e094229b6fcd19d68
Verify each with:
cosign verify ghcr.io/anycloud-sh/backmesh-runner@sha256:a3642da07f8991fb73bd8995af449dffe126cfb042e13d9c8005b0749dd4d703 --certificate-identity https://github.com/anycloud-sh/backmesh/.github/workflows/image.yml@refs/tags/v0.3.0 --certificate-oidc-issuer https://token.actions.githubusercontent.com
cosign verify ghcr.io/anycloud-sh/backmesh-listener@sha256:301d1545631cf018c97d9bc8730a14de31cd13e5dff1311e094229b6fcd19d68 --certificate-identity https://github.com/anycloud-sh/backmesh/.github/workflows/image.yml@refs/tags/v0.3.0 --certificate-oidc-issuer https://token.actions.githubusercontent.comPins anycloud 0.1.75; each CLI binary embeds compatibility.json, which backmesh upgrade reads. checksums.txt holds their sha256 digests.