Tie builds to release changes
Connect
SPIRITT
CodemagicCodemagic
Carry mobile builds through the gate
Operate Codemagic build queues, repository onboarding, and release evidence with verified outcomes rather than launch-and-forget jobs. SPIRITT brings the applications, workflows, builds, caches, and variable groups into one working operation, coordinates the next steps across your connected tools, and keeps the outcome in view.
What you can do with Codemagic.
Builds start with the right context
Inspect application workflows and start a build for the selected branch or tag. Follow build history until the actual outcome is known.
Repositories enter a repeatable process
Add approved repositories to Codemagic, verify the created application, and connect onboarding work to the engineering checklist.
Build configuration stays accountable
Inspect application caches and variable-group settings, reconcile approved configuration changes, and maintain a change record without exposing secret values.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Create a SPIRITT workspace for your Codemagic operation. Describe the outcome, the records involved, and what finished work should look like.
02
Connect Codemagic
Connect Codemagic with access to the applications, workflows, builds, caches, and variable groups needed for the mission. Connect companion apps for the handoffs you want SPIRITT to run.
03
Delegate a mission
Ask SPIRITT to operate Codemagic build queues, repository onboarding, and release evidence with verified outcomes rather than launch-and-forget jobs. Set the approval points and cadence, then let it carry the work through.
Hand over a mission.
Choose a mission. Make it yours.
Put Codemagic to work.
Carry mobile builds through the gate
Questions
Codemagic, with SPIRITT.
01Can SPIRITT start and follow builds?+
Inspect application workflows and start a build for the selected branch or tag. Follow build history until the actual outcome is known.
02Can it onboard repositories into Codemagic?+
Add approved repositories to Codemagic, verify the created application, and connect onboarding work to the engineering checklist.
03Can it manage build configuration hygiene?+
Inspect application caches and variable-group settings, reconcile approved configuration changes, and maintain a change record without exposing secret values.
04Does a started build mean a release is shipped?+
No. SPIRITT follows the Codemagic build result and reports what that result proves. App-store publication depends on the selected workflow and its actual outcome; a queued build, cache-deletion acceptance, or preview action is not a successful release.
05How do I set up Codemagic with SPIRITT?+
Open a SPIRITT workspace, connect Codemagic, and describe the mission. Choose the applications, workflows, builds, caches, and variable groups it should use and the actions it can take. Add the companion connections for messages, records, or deliverables outside Codemagic.
06How does SPIRITT follow through on Codemagic work?+
SPIRITT follows build history to the actual result, connects failures to the engineering owner, and carries verified build evidence into the release checklist. Queue acceptance is never reported as a completed build.