scriptworker 0.8.1

TaskCluster Script Worker

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

Usage

• Create a config file. By default scriptworker will look in ./scriptworker.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.constants.DEFAULT_CONFIG.

Credentials can live in ./scriptworker.json, ./secrets.json, ~/.scriptworker, or in environment variables: TASKCLUSTER_ACCESS_TOKEN, TASKCLUSTER_CLIENT_ID, and TASKCLUSTER_CERTIFICATE.

• If using either verify_chain_of_trust or sign_chain_of_trust, you will also need a cot_config.json, which is either specified as the 2nd argument in the commandline, or in ./cot_config.json.

• Launch: scriptworker [config_path] [cot_config_path]

Testing

Note: GPG tests require gpg 2.0.x!

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