Skip to content
Configuration for Taskcluster at
Branch: master
Clone or download
djmitche Merge pull request #4 from djmitche/worker-pool-star
Add missing *s in project-admin:* role
Latest commit a590e13 Oct 17, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github fix CODEOWNERS Oct 11, 2019
config Merge pull request #4 from djmitche/worker-pool-star Oct 17, 2019
generate Allow configuration of min/maxCapacity Oct 17, 2019
.gitignore Initial commit Sep 25, 2019
LICENSE Initial commit Sep 25, 2019 Bug 1588873 - update README Oct 16, 2019 update name of google provider Oct 16, 2019 update tc-admin Oct 14, 2019 Bug 1588873 - set up and use grants.yml Oct 16, 2019


This repository defines a tool to manage the runtime configuration for the Taskcluster deployment at It uses tc-admin to examine and update the deployment. See that library's documentation for background on how the process works.


A Taskcluster deployment has a collection of resources such a roles, hooks, and worker pools, that define its behavior. These can all be managed via the Taskcluster API, but managing them by hand is error-prone and difficult to track over time. This tool exists to manage those resources in a controlled, observable way. It does so by making API calls to determine the current state, examining this repository to determine the desired state, and then "applying" the necessary changes to get from the former to the latter.

A deployment is also defined by a number of back-end settings that are not available in the API. These are defined by the service configuration. While this tool cannot change those settings, it does depend on them, and they are described here.

Quick Start

If you would like to propose a change to the configuration of the Community-TC deployment, you are in the right spot. You should already have an understanding of the resources you would like to modify. See the Taskcluster Documentation or consult with the Taskcluster team -- we are responsible for managing this deployment, and happy to help -- if you need assistance.

Begin by installing this app by running pip install -e . in this directory. Then, run


This will show you the current difference between what's defined in your local repository and the runtime configuration of the deployment. Most of the time, there should be no difference.

Then, change the configuration in this repository, using the comments in the relevant files as a guide. After making a change the the configuration, you can examine the results by running tc-admin diff again. If you are adding or removing a number of resources, you can use --ids-only to show only the names of the added or removed resources. See tc-admin --help for more useful command-line tricks.


This deployment follows the convention of project namespaces. Each project has a its own worker pools, and user roles can be given "admin" access to the project.

Repositories are granted scopes via the Taskcluster-github scheme. Each repository is associated with a project, and scopes granted to the repository should be associated with that project. This occurs within config/projects.yml.

You can’t perform that action at this time.