---
title: "Codemagic | Skills We Assign For | Azendo"
description: "Codemagic for mobile CI/CD — managed macOS builds, signing and store publishing, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/codemagic/"
---

[Skills](https://azendo.co/skills/) CI and delivery 

# Codemagic.

Codemagic is a CI/CD service built specifically for mobile, with managed macOS build machines, code signing handling, and direct publishing to TestFlight and Google Play. It removes the need to operate Apple build hardware.

## Where Codemagic fits on a long engagement.

iOS builds require macOS, which is the constraint that makes mobile CI different from everything else. The alternatives are a hosted macOS runner or a physical Mac somebody maintains, and the second is a single point of failure that is invariably discovered at the worst moment.

Mobile-specific services handle the parts general CI platforms make awkward: signing certificates, provisioning profiles, and publishing to both stores. A general-purpose runner can do all of it, but the configuration is longer and the failure modes are less obvious.

## What an assigned team does with Codemagic.

Build minutes on managed macOS are expensive enough that pipeline efficiency is a cost question rather than a convenience one. Caching dependencies and running the right workflows on the right triggers has a directly visible effect on spend.

Treating that as ongoing rather than a setup task is part of how platform capacity is assigned under [devops as a service](https://azendo.co/services/cloud-and-devops/).

## What we use Codemagic for.

* iOS builds without owning a Mac Managed macOS runners, so no physical machine is a release dependency.
* Publishing to both stores from one pipeline TestFlight and Play submissions from the same workflow rather than two manual processes.
* Keeping build spend in proportion Caching and trigger discipline, because managed macOS minutes are the expensive resource.

## How Codemagic capacity is assigned.

Mobile CI is scoped with the mobile capacity it serves, under the same agreement rather than as a separate engagement.

## Roles we assign Codemagic for

* [Flutter Developer Mobile development](https://azendo.co/services/mobile-development/flutter-developer/)

## Service lines it sits in

* [Mobile development](https://azendo.co/services/mobile-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in ci and delivery

* [GitHub Actions — skill we assign for](https://azendo.co/skills/github-actions/)
* [Jenkins — skill we assign for](https://azendo.co/skills/jenkins/)
* [GitLab CI — skill we assign for](https://azendo.co/skills/gitlab-ci/)
* [Fastlane — skill we assign for](https://azendo.co/skills/fastlane/)
* [TestFlight — skill we assign for](https://azendo.co/skills/testflight/)
* [App Store Connect — skill we assign for](https://azendo.co/skills/app-store-connect/)
* [Play Console — skill we assign for](https://azendo.co/skills/play-console/)
* [CodePush — skill we assign for](https://azendo.co/skills/codepush/)

## Tell us what your roadmap needs Codemagic for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)