CI/CD
Release every merge to production from your pipeline with one CLI line, and keep the three disciplines that make shipping every commit safe.
Your pipeline runs one CLI line after the build on every merge, and devices take the release on their next check. The short version is the site's continuous delivery for mobile page. Read Ship every commit once, then your provider's recipe.
CI from your Git host
Azure DevOps
An azure-pipelines.yml that releases every push to main.
Bitbucket Pipelines
A bitbucket-pipelines.yml that releases every push to main.
Gitea Actions
A .gitea/workflows/release.yml that releases every push to main.
GitHub Actions
A .github/workflows/release.yml that releases every merge to main.
GitLab CI/CD
A .gitlab-ci.yml that releases every push to the default branch.
Mobile build services
Bitrise
A bitrise.yml with a tag Workflow for the store build and a push Workflow on main.
Capawesome Cloud
Tag automations that register the store builds, and a web automation that releases every push to main.
Codemagic
A codemagic.yaml that registers the store builds and releases every push to main.
EAS Build
Store builds that register with an EAS secret, and a .eas/workflows/release.yml that releases every push to main.
Xcode Cloud
An archive workflow that registers every iOS store build, with the ci_post_clone.sh that installs Node.js.
Last updated on
Tag releases in your telemetry
Read the running release from the SDK and attach it to Sentry, OpenTelemetry or any tracker, so a crash names the bundle that caused it.
Ship every commit
Run npx hotcodepush release create after the build on every merge to main, with the API token and the signing key held as CI secrets.