Build Pipeline Triggers

Codemagic runs configured build pipelines for iOS, Android, and Flutter projects on events like a merge or a tag. A Beam agent reads the repository event, applies the customer's approved rule for which branches or tags should build, and starts the matching pipeline instead of an engineer doing it manually. It can also notify the team once the pipeline finishes, whether the result is a pass or a failure. Changes to which pipeline runs for which branch, and any failure tied to signing or provisioning, are routed to a human to resolve.

App Store Deployment Handoff

Codemagic can publish a finished build to App Store Connect or Google Play once it passes. A Beam agent watches for a successful build that matches the approved release criteria, then hands it to the configured publishing step and notifies the release owner that a new build is ready for the store. It does not decide what counts as release ready; that rule is set by the customer in advance. Any failed submission, metadata rejection, or store review issue is routed to a human for the fix.

Build Failure Notification

When a Codemagic pipeline fails, the log points to a specific step, such as a test, a signing certificate, or a dependency error. A Beam agent reads the failure reason, applies the approved rule for who owns that type of failure, and notifies that person with the relevant log excerpt attached instead of the whole team having to dig through the console. It can also reopen a linked ticket if one exists for the branch. Recurring failures with an unclear cause are routed to a human engineer to investigate.