Remote builds are in early access. Reach out to the Revyl team before using
this feature so we can enable it for your workspace.
What you can use them for
- Cloud builds for agents. A local agent or cloud agent can change code, run a build, and get a real app artifact back without needing your machine.
- Fast CI. Trigger iOS or Android builds from lightweight CI jobs instead of maintaining mobile runners yourself.
- PR previews. Build and test pull requests automatically, with Revyl posting status back to GitHub.
- One place for builds and tests. The finished build is already in Revyl, so the next step is launching a device or running a test.
FAQ
What do I configure?
Your.revyl/config.yaml defines customer-named profiles. Each profile owns an
iOS and/or Android recipe with its Revyl app, ordered commands, and output
artifact. revyl build --profile <name> --platform ios|android --remote
selects one recipe; no profile is stored as active or default.
What does Revyl build?
For iOS, produce a simulator.app or an archive that contains one. For
Android, produce an installable .apk.
Requirements
- Revyl CLI installed and authenticated
- An app in Revyl to receive the builds (
revyl app createor the Apps page) - A runnable profile/platform recipe in
.revyl/config.yaml(the quickstart walks through this)
Remote builds are metered by build minutes. If your plan doesn’t include build
credits, triggering a build returns a billing error. Upgrade your plan or
contact [email protected].
Docs
Quickstart
Install the CLI, run init, and start your first build.
Configuration
The
build: section of .revyl/config.yaml and every CLI flag.Toolchain Images
Available images and installed tools.
Caching
Use automatic compilation caches and configured path caches.