Skip to main content
Tesser can run your GitHub Actions jobs. Each job gets its own new box, and the box starts from the disk the job’s last successful run left behind: the checkout, the home directory with its package stores and build caches, the tool cache, and Docker’s images and layers. Installs and builds then redo only what changed. GitHub Actions on Tesser is not open to every org yet. Tesser turns it on org by org, and tesser ci connect is refused in an org where it is not on (who can use it).

Connect a GitHub organization

An admin of the Tesser org runs this once:
It prints a link. Someone who owns the GitHub organization opens it and installs the Tesser GitHub App there. After that, jobs in the GitHub organization’s repositories can run on the Tesser org’s boxes.

Run a job on Tesser

Point a job’s runs-on at a Tesser label:
The number in the label is the box’s vCPU count. Nothing else in the workflow has to change. clean: false keeps untracked files such as node_modules in the checkout between runs; without it, actions/checkout deletes them, and only what lives outside the checkout carries over. The box is removed when the job ends and is billed by the second, like any box.

See what your jobs did

tesser ci shows which disk each job started from, or why it started cold. To run a job on a clean disk, use the label with -no-snapshot, such as runs-on: tesser-4vcpu-no-snapshot. GitHub Actions jobs has the exact rules: the labels and sizes, which branch or pull request a job reads and saves, forks, and how long a job’s disk is kept.