servo/etc/taskcluster/macos
2018-11-15 17:38:13 +01:00
..
config generic-worker on macOS: read-only config 2018-11-15 17:38:13 +01:00
modules/pillar generic-worker on macOS: configure livelog 2018-11-15 17:38:13 +01:00
states generic-worker on macOS: read-only config 2018-11-15 17:38:13 +01:00
.gitignore Initial agentless SaltStack config for generic-worker on macOS 2018-11-15 17:38:13 +01:00
README.md generic-worker on macOS: run as unprivileged user, start as a service 2018-11-15 17:38:13 +01:00
salt-ssh generic-worker on macOS: run as unprivileged user, start as a service 2018-11-15 17:38:13 +01:00
Saltfile generic-worker on macOS: run as unprivileged user, start as a service 2018-11-15 17:38:13 +01:00

macOS

This is the configuration for the proj-servo/macos worker type. These macOS workers are configured with SaltStack in agentless mode.

Either run ./salt-ssh to automatically install salt-ssh in machs existing Python virtualenv, or install salt-ssh through some other mean and run in from this directory.

cd etc/taskcluster/macos
./salt-ssh '*' test.ping
./salt-ssh '*' state.apply test=True

Servers

Servers are provisioned manually from MacStadium. The config/roster file lists them by DNS name.

Taskcluster secrets

This SaltStack configuration has a custom module that uses Taskclusters secrets service. These secrets include an [authentication token]( Youll need to authenticate with a Taskcluster client ID that has scope secrets:get:project/servo/*. This should be the case if youre a Servo project administrator (the project-admin:servo role).

Workers client ID

Workers are configured to authenticate with client ID project/servo/worker/macos/1. This client has the scopes required to run tasks for this worker type.