brimble ci manages CI runners, the Brimble sandboxes that run your GitHub organization’s Actions jobs.
ci-runner and runners.
Before you start
CI runners need a GitHub organization connected to your account and a plan that includes CI runners. Each organization has one runner. See CI runners for the full setup, including the GitHub App permission an organization owner must accept.Create a runner
In a script,
--account and --name are required, and --mode defaults to per_job.
List and inspect
get is also show and info. list is also ls.
Change or delete a runner
update with no flags asks what to change. It also accepts --mode, --size, --region, --max-concurrency, and --enable to turn a runner back on.
Deleting a runner detaches its sandboxes and removes the runner. The sandboxes are not deleted.
Jobs and logs
jobs lists the GitHub Actions jobs that asked for this runner, newest first, with --page and --limit to page through them. logs prints one job’s log; with no job ID it asks you to pick from the list.
Sandboxes on a reuse runner
Areuse runner needs at least one attached sandbox to run jobs.
attach offers an existing ready sandbox or a new one. Pass --sandbox <name-or-id> to attach an existing sandbox, or --new --size sbx.micro --region us-east-1 to create one. detach asks which sandbox to remove. Detaching stops the runner in that sandbox and returns the sandbox to its normal expiry.
See also
- CI runners, the concept, the setup, and the
runs-onlabel in a workflow.