---
title: Native Build Integrations
description: Connect Capawesome Cloud native builds to your toolchain — CI/CD pipelines like GitHub Actions, GitLab CI/CD, Azure DevOps, Bitbucket Pipelines, and error monitoring with Sentry.
---

# Integrations

Connect native builds to the rest of your toolchain — trigger builds from your CI/CD pipeline, or upload source maps to your error monitoring service during the build.

## CI/CD pipelines

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

<div class="grid cards" markdown>

-   :material-microsoft-azure-devops:{ .lg .middle } **Azure DevOps**

    ---

    [:octicons-arrow-right-24: Set up](azure-devops.md)

-   :simple-bitbucket:{ .lg .middle } **Bitbucket Pipelines**

    ---

    [:octicons-arrow-right-24: Set up](bitbucket-pipelines.md)

-   :simple-githubactions:{ .lg .middle } **GitHub Actions**

    ---

    [:octicons-arrow-right-24: Set up](github-actions.md)

-   :simple-gitlab:{ .lg .middle } **GitLab CI/CD**

    ---

    [:octicons-arrow-right-24: Set up](gitlab-ci.md)

</div>

!!! tip "Official GitHub Action"

    On GitHub? The official [`cloud-build-action`](https://github.com/capawesome-team/cloud-build-action){:target="_blank"} triggers a native build in a single step — see [GitHub Actions](github-actions.md).

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, store it as a CI secret, and log in with `--token`.
2. **Trigger the build** — `apps:builds:create --platform ios` (or `android`), with `--git-ref` pointing at the commit to build and `--yes` to skip confirmation prompts.
3. **Submit (optional)** — pass `--destination` to send the finished build to TestFlight or Google Play, turning the pipeline into a full release.

Pin the CLI version (`@capawesome/cli@<version>`) so pipelines are reproducible, and prefer manual dispatch over auto-on-merge so builds run when you decide.

For signing certificates, environments, and store submissions in CI, see [Certificates](../certificates/index.md), [Environments](../environments.md), and [App Store Publishing](../../app-store-publishing/index.md). For ready-to-run pipelines, see [Sample Projects](../sample-projects.md).

## Error monitoring

Upload source maps to your error monitoring service during the build to get readable stack traces.

<div class="grid cards" markdown>

-   :simple-sentry:{ .lg .middle } **Sentry**

    ---

    [:octicons-arrow-right-24: Set up](sentry.md)

</div>