Scriptworker implements the TaskCluster worker model, then launches a pre-defined script.
This worker was designed for Releng processes that need specific, limited, and pre-defined capabilities.
Free software: MPL2 license
- Create a config file. By default scriptworker will look in
./config.json
, but this config path can be specified as the first and only commandline argument. There is an example config file, and all config items are specified in scriptworker.config.DEFAULT_CONFIG.
- Launch:
scriptworker [config_path]
Without integration tests,
NO_TESTS_OVER_WIRE=1 python setup.py test
With integration tests, first create a client with the assume:project:taskcluster:worker-test-scopes
scope.
Then create a ./secrets.json
or ~/.scriptworker
that looks like:
{ "integration_credentials": { "clientId": "...", "accessToken": "...", "certificate": "..." } }
(certificate
is only specified if using temp creds)
then
python setup.py test