Skip to main content
Bitrise builds on macOS machines it hosts. mobster ci init --host bitrise writes a workflow with the steps. CI has the parts every host shares.

Set it up

It writes bitrise.yml. When that file exists, it leaves it as it is and writes the mobster workflow to .mobster/hosts/bitrise.yml for you to merge. Then add MOBSTER_CI_TOKEN as a Secret of the Bitrise app, trigger the mobster workflow on pull requests, commit the file and open a pull request. The workflow clones the repository, installs Mobster for Mac with Homebrew, runs mobster sim doctor --fix, runs mobster ci run, and deploys .mobster/ci as the build’s artifacts even when a check fails. The target branch comes from BITRISEIO_GIT_BRANCH_DEST. Bitrise gets no comment from Mobster: GitHub and GitLab are the hosts where mobster ci comment posts.

Sign in with a CI token

The job signs in with a CI token, not with Mobster for Mac. It is part of your plan, adds no seat and counts no runs. It licenses simulator checks only (mobster ci run and mobster test), it ends after 90 days unless you choose up to 365, and it never licenses an iPhone. Make one with mobster account ci-token create NAME or in the console under Settings › CI tokens, and revoke it from either. Store it as MOBSTER_CI_TOKEN, as a secret of the service. mobster ci doctor in the job checks that it is live and says what to fix if it isn’t.

What this runner doesn’t do

A hosted Mac has no iPhone, so the checks run on simulators. To test on a phone, use a Mac of yours.