Open gregtatum opened 5 months ago
This involves manipulating the task graph that is generated. The task graph is a JSON file that describes all of the information to run our pipeline. This is a good first bug if you want to figure out how to work with the taskgraph. It's probably a bit more involved.
You can generate the graph locally with:
task preflight-check -- --only task_group
Then open:
artifacts/full-task-graph.json
You can also diff the taskgraph to see how the results have changed by first committing your work, and then run:
BASE_REV=main task taskgraph-diff
The kind.yml
files describe an individual task, and include a command:
section of what is run.
For example:
The work here would be to write a "transform" that would add the requirements installation to the command section. I would look through all the implementations of "command:" to get an idea how it works.
A good example of a "transform" is the "cast_to" transform. The implementation is here:
And it can be seen in use here:
You can also refer to the taskgraph documentation: https://taskcluster-taskgraph.readthedocs.io/en/latest/
This will help with our local testing config, and simplify our kind.yml files.
Something like: