Scriptworker Readme
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.yaml, 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.yaml, ./secrets.json, ~/.scriptworker.
Launch: scriptworker [config_path]
Testing
Without integration tests install tox, then
NO_CREDENTIALS_TESTS=1 uv run tox -e py311
Without any tests connecting to the net, then NO_TESTS_OVER_WIRE=1 uv run tox -e py311
With integration tests, first create a client in the Taskcluster UI with the scopes:
queue:cancel-task:test-dummy-scheduler/* queue:claim-work:test-dummy-provisioner/dummy-worker-* queue:create-task:lowest:test-dummy-provisioner/dummy-worker-* queue:define-task:test-dummy-provisioner/dummy-worker-* queue:get-artifact:SampleArtifacts/_/X.txt queue:scheduler-id:test-dummy-scheduler queue:schedule-task:test-dummy-scheduler/* queue:task-group-id:test-dummy-scheduler/* queue:worker-id:test-dummy-workers/dummy-worker-*
Then generate a no priviledge personal access token in Github for the scriptworker_github_token (to avoid rate limiting) and create a ./secrets.json or ~/.scriptworker that looks like:
{
"integration_credentials": {
"clientId": "...",
"accessToken": "...",
}
"scriptworker_github_token": "..."
}
then to run all tests: uv run tox
Release files for scriptworker 64.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| scriptworker-64.0.0.tar.gz | 107.1 kB | With provenance | Details for scriptworker-64.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scriptworker-64.0.0-py3-none-any.whl | Python 3 | none | any | Details for scriptworker-64.0.0-py3-none-any.whl |
Total release size: 192.6 kB
Release files / scriptworker-64.0.0.tar.gz
| Download URL | scriptworker-64.0.0.tar.gz |
|---|---|
| Size | 107.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
901ac0714d1c3afcfc8835d4aac28ba2d3c2fae7de1a12fb4eb24aa696edc1e2
|
|
BLAKE2b-256 checksum How to use checksums |
839f3b0a777d57e3965c02bd575c6a82295572953727ab7d53bb21a30bb48922
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / scriptworker-64.0.0-py3-none-any.whl
| Download URL | scriptworker-64.0.0-py3-none-any.whl |
|---|---|
| Size | 85.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
281d6d6d15a450b91d61dcb89e72da087b6b37aca6689977330d1c67b8e41a91
|
|
BLAKE2b-256 checksum How to use checksums |
a67dde09245984249b6978b613774d25a99fc0aa6dd4ec42cd1ee141c3a6d082
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logSecurity for scriptworker 64.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for scriptworker-64.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
