In the future there will be a brew package, but for now you have to manually download the macOS binary.
-
Download the binary for your system:
sudo curl --output /usr/local/bin/alloy-runner https://alloy-runner-downloads.s3.amazonaws.com/latest/binaries/alloy-runner-darwin-amd64
You can download a binary for every available version as described in Bleeding Edge - download any other tagged release.
-
Give it permissions to execute:
sudo chmod +x /usr/local/bin/alloy-runner
The rest of commands execute as the user who will run the Runner.
-
Install the Runner as service and start it:
cd ~ alloy-runner install alloy-runner start
Voila! Runner is installed and will be run after a system reboot.
-
Stop the service:
alloy-runner stop
-
Download the binary to replace the Runner's executable:
curl -o /usr/local/bin/alloy-runner https://alloy-runner-downloads.s3.amazonaws.com/latest/binaries/alloy-runner-darwin-amd64
You can download a binary for every available version as described in Bleeding Edge - download any other tagged release.
-
Give it permissions to execute:
chmod +x /usr/local/bin/alloy-runner
-
Start the service:
alloy-runner start
Make sure that you read the FAQ section which describes some of the most common problems with AlloyCI Runner.
Note: The service needs to be installed from the Terminal by running its GUI interface as your current user. Only then will you be able to manage the service.
Currently, the only proven to work mode for macOS is running service in user-mode.
Since the service will be running only when the user is logged in, you should enable auto-login on your OSX machine.
The service will be launched as one of LaunchAgents
. By using LaunchAgents
,
the builds will be able to do UI interactions, making it possible to run and
test on the iOS simulator.
It's worth noting that OSX also has LaunchDaemons
, the services running
completely in background. LaunchDaemons
are run on system startup, but they
don't have the same access to UI interactions as LaunchAgents
. You can try to
run the Runner's service as LaunchDaemon
, but this mode of operation is not
currently supported.
You can verify that the Runner created the service configuration file after
executing the install
command, by checking the
~/Library/LaunchAgents/alloy-runner.plist
file.
In order to upgrade the LaunchAgent
configuration, you need to uninstall and
install the service:
alloy-runner uninstall
alloy-runner install
alloy-runner start