Build and ship
Build and ship
Task guides for apps, pipelines, builds, sources, signing, and delivery.
These guides each do one job on an Oore instance that already runs. If you are starting from nothing, follow Get started first. It strings the tasks below into one path for Android and one for iOS.
Set up what Oore builds
- Create an app for each repository.
- Configure a pipeline in the UI from a template.
- Move a pipeline into
.oore.yamlso it changes with the code. This page also helps you pick a format. - Use secrets in a pipeline for tokens and keys.
- Set triggers, timeouts, and approvals.
- Run two workflows from one file, each with its own signing and publishing.
- Add pipelines from the repository.
Run and control builds
- Trigger a build by hand.
- Approve a build that waits for a maintainer.
- Cancel a build.
- Retry a store upload without rebuilding.
Build on every push and pull request
These guides need External Access.
- Connect GitHub or connect GitLab.
- See builds on pull requests, with app size and size budgets.
- Troubleshoot source webhooks.
Sign builds
- Add Android signing, and keep local Gradle signing working.
- Configure App Store Connect signing, the shortest path for iOS.
- Configure manual iOS signing with certificates and profiles you export.
- Move credentials into the app library so each workflow signs with its own keys.
Deliver builds
| Goal | Guide |
|---|---|
| Let your team install every build | Share builds with testers through Oore |
| Get a file from a build | Download a build artifact |
| Install an APK on a phone | Install an Android build |
| Install an iOS build on a test iPhone | Register an iOS test device, then install it |
| Send builds to Google Play | Publish to Google Play |
| Send builds to TestFlight or the App Store | Publish to TestFlight and the App Store |
| Move a tested build to production | Promote builds between environments |
Next step
New to Oore? Start with Choose your path. Otherwise, pick the guide for your goal above.