axs build
How it works
Builds and tests for your agents, on your own machines.
axs build -- <cmd> ships the changed files of your checkout to whichever of your connected machines is free and
warm, runs the command there and prints a short summary made for an agent's context. The exit code is the
command's own.
axs build -- ./gradlew testGet started
- Install the axs CLI and run
axs login. Build uses the same login as brain. - Add a machine: any box with Docker.
- Run builds and tests with
axs build -- <cmd>from inside a checkout, or let the route hook send your agent's builds there.
Where the speed comes from
- One long lived container per project per machine. Gradle and Kotlin daemons, build folders and caches stay warm between jobs.
- Only files the machine does not have yet are uploaded; files git ignores stay home.
- Among the machines with room, one with a warm container for the project wins.
- A new run from the same checkout with the same command cancels the older one.
- Outputs such as jars and reports come back to their normal paths when the job ends.
The dashboard
In app.axs.sh the build section of a team has Jobs (live, with the log), Machines and
Settings (CLI login and secrets).