Skip to content

Integrations

Trigger native builds from your CI/CD pipeline. The setup is the same across providers — only the pipeline syntax differs.

Official GitHub Action

On GitHub? The official cloud-build-action triggers a native build in a single step — see GitHub Actions.

How it works

The build itself always runs on Capawesome Cloud's hosted macOS runners — so your CI job doesn't need a Mac, Xcode, or any native toolchain. It only authenticates and starts the build. Every pipeline follows the same shape:

  1. Authenticate — create an API token in Capawesome Cloud, store it as a CI secret, and log in with --token.
  2. Trigger the build — start it with apps:builds:create --platform ios (or android), pointing at the commit you want to build.
  3. Submit (optional) — pass --destination to send the finished build to TestFlight or Google Play, turning the pipeline into a full release.

A few recommendations that apply to every provider:

  • Pin the CLI version (@capawesome/cli@<version>) so pipelines are reproducible.
  • Use --git-ref to build a specific branch, tag, or commit rather than whatever happens to be checked out.
  • Pass --yes to skip confirmation prompts in non-interactive environments.
  • Prefer manual dispatch over auto-on-merge so builds run when you decide.

For signing certificates, environments, and store submissions in CI, see Certificates, Environments, and App Store Publishing. For complete, ready-to-run pipelines, see Sample Projects.