Where Does Codemagic Store Build Config?
Codemagic reads build config from codemagic.yaml at each repo root, with signing files, variables, and schedules managed in the web app.
Last updated
Codemagic configures mobile builds per repository through codemagic.yaml at the root. Workflows name scripts, test steps, and publish targets for iOS and Android from one file. The web app adds signing identities, variables, and schedules around it.
Mobile signing dominates setup complexity. Certificates and profiles upload once in the dashboard then reference by name, keeping secrets out of git. Build machines stay ephemeral, so everything durable lives in repo plus dashboard.
Where Codemagic stores this, by platform
codemagic.yaml
Build workflows per repo for mobile targets. Signing identities upload in dashboard. Validate by pushing.
codemagic.yaml
Same repo relative config for macOS iOS builds. Xcode versions pin in workflows. Apple credentials live in dashboard.
codemagic.yaml
Windows workflows share the identical repo file. Signing references stay dashboard side. No local state needed.
Frequently asked questions
How do I add Codemagic to a repo?
Add codemagic.yaml at root with workflows for each platform target, then push to trigger. The docs validate schema with examples per stack. Environment variables inject secrets at runtime.
Where do Codemagic signing files go?
Upload keystores, provisioning profiles, and certificates in the web UI under code signing identities. Reference them by name from YAML without committing secrets. iOS builds need Apple credentials too.
Notice an outdated path? Let us know.