Build
From the editor to the App Store and Google Play.
Choose TestFlight, .apk or .aab in the editor. Armori.ca queues the build and a builder makes it, while you follow the log live.
TestFlight
Archive, sign and upload to App Store Connect, with your own Apple credentials per workspace.
.apk
An installable file to test your app straight away on an Android device.
.aab
The bundle for Google Play, signed with an upload key of its own per app.
Builders: a Mac does the work
A builder is a Mac that checks in with Armori.ca and picks up builds from the queue. Installing it is a single command; after that it keeps itself up to date.
If a builder drops out for a moment, it keeps building and sends what was missing when it comes back. Even a server restart does not break a build.
Build number and bundle ID
Every build gets a new build number; without an ID of its own, your app gets one.
Terminal in the browser
Steps and log stream in live; the full log is kept.
Secrets only during the build
Keys are on the builder only during the build and only travel with that one build.
🚢 In the village this is called…
Village glossary →⚓
The shipyard
The builder: a Mac that puts your ship together.
🚢
The big ship
A build for the stores. It waits its turn in the queue at the yard.
🧭
The sea trial
TestFlight: your testers sail along first.
🌊
The crossing
Publishing in the App Store or Google Play. A menhir next to the hut for every release is in the cauldron.