axs build
Settings
Per repo config, secrets and CLI tokens.
.mb.toml
Gradle, Node, Go and Cargo projects work without config. A .mb.toml in the repo root changes the defaults; every
key is optional:
project = "billing-api" # default: the name of the origin remote
build = "ci/Dockerfile" # or: image = "eclipse-temurin:21-jdk"
caches = ["/root/.gradle"] # container paths kept between jobs
outputs = ["build/libs", "build/test-results"] # copied back after the job
docker = true # the host's Docker socket, for Testcontainers
timeout = "60m"| Detected | Image | Caches | Outputs |
|---|---|---|---|
| Gradle | eclipse-temurin:21-jdk | /root/.gradle | build/libs |
| Node | node:22 | /root/.npm, /root/.cache, /root/.local/share/pnpm | dist |
| Go | golang:1.27 | /go/pkg/mod, /root/.cache/go-build | none |
| Cargo | rust:1 | /usr/local/cargo/registry | target/release |
A folder with its own build file (such as web/ with a package.json in a Go repo) gets its own container and
caches. Repos that use Testcontainers get the Docker socket on their own.
Secrets
Secrets reach jobs as environment variables and never travel with the sources. Set them for one project or for all
(*); the value is read from stdin:
echo -n "$TOKEN" | axs build secret set billing-api NPM_TOKEN
axs build secret ls
axs build secret rm billing-api NPM_TOKENThe dashboard has the same under build, Settings, Secrets. Values never come back.
CLI tokens
axs login is all most people need. For a script, build, Settings, New token makes a user API token (mbu_...)
bound to you and the team:
axs build login mbu_...