Taskcluster history from https://firefox-ci-tc.services.mozilla.com deployment for:
For https://community-tc.services.mozilla.com history, please see community-history.
Please note, until 9 November 2019 this repository stored the history for the https://taskcluster.net deployment. On 9 November 2019 the https://taskcluster.net deployment was decommissioned and the https://firefox-ci-tc.services.mozilla.com was instated.
The files are named after the entities themselves, except for the following character conversions:
*->★
This conversion avoids illegal filenames.
/->⁄
Rather than creating nested subdirectories, this conversion avoids directory names colliding with entity filenames.
go get github.com/taskcluster/mozilla-history@v1.0.0
unset TASKCLUSTER_CLIENT_ID TASKCLUSTER_ACCESS_TOKEN TASKCLUSTER_CERTIFICATE
export TASKCLUSTER_ROOT_URL='https://firefox-ci-tc.services.mozilla.com'
mozilla-history
This will populate subdirectories Clients, Hooks, Roles and WorkerPools
of the current directory.
You can automate this reporting process by setting up a cron job to execute run-report.sh at regular intervals.
- Valid Taskcluster credentials must be set in the environment variables:
TASKCLUSTER_CLIENT_IDTASKCLUSTER_ACCESS_TOKEN
run-report.shexecutesaudit.shaudit.shschedules tasks for each worker pool to extract worker implementation details from logs- Results are stored in the
WorkerPoolsdirectory mozilla-historystores Taskcluster configurations in their respective directories:- Hooks definitions in
Hooks/ - Roles definitions in
Roles/ - WorkerPool definitions in
WorkerPool/
- Hooks definitions in
build-docs-history.shcollects every past revision ofWorkerVersions/workers.jsonintodocs/history.json, which feeds the two GitHub Pages views:docs/index.html— the current report plus the full history tables and graphsdocs/migration.html— an animated month-by-month timeline of the docker-worker to generic-worker migration and of the generic-worker version rollout