1Skia Infrastructure 2=================== 3 4This directory contains infrastructure elements. 5 6 7Tasks and Jobs 8-------------- 9 10Files in this directory define a DAG of tasks which run at every Skia commit. A 11task is a small, self-contained unit which runs via Swarming on a machine in the 12pool. Tasks may be chained together, eg. one task to compile test binaries and 13another to actually run them. 14 15Jobs are collections of related tasks which help define sub-sections of the DAG, 16for example, to be used as try jobs. Each job is defined as an entry point into 17the DAG. 18 19The tasks.json file in this directory is the list of tasks and jobs for 20the repo. Note that tasks.json is NEVER edited by hand but generated via 21gen_task.go and the input files enumerated below. The 22[Task Scheduler](https://skia.googlesource.com/buildbot/+/master/task_scheduler/README.md) 23reads the tasks.json file at each commit to determine which jobs to run. For 24convenience, gen_tasks.go is provided to generate tasks.json and also to test it 25for correct syntax and detecting cycles and orphaned tasks. Always edit 26gen_tasks.go or one of the following input JSON files, rather than tasks.json 27itself: 28 29 * cfg.json - Basic configuration information for gen_tasks.go. 30 * jobs.json - The list of all jobs to run. Edit this to add or remove 31 bots. 32 33Whenever gen_tasks.go, any of the above JSON files, or assets are changed, you 34need to run gen_tasks.go to regenerate tasks.json: 35 36 $ go run infra/bots/gen_tasks.go 37 38Or: 39 40 $ cd infra/bots; make train 41 42There is also a test mode which performs consistency checks and verifies that 43tasks.json is unchanged: 44 45 $ go run infra/bots/gen_tasks.go --test 46 47Or: 48 49 $ cd infra/bots; make test 50 51 52Recipes 53------- 54 55Recipes are the framework used by Skia's infrastructure to perform work inside 56of Swarming tasks. The main elements are: 57 58 * recipes.py - Used for running and testing recipes. 59 * recipes - These are the entry points for each type of task, eg. compiling 60 or running tests. 61 * recipe_modules - Shared modules which are used by recipes. 62 * .recipe_deps - Recipes and modules may depend on modules from other repos. 63 The recipes.py script automatically syncs those dependencies in this 64 directory. 65 66 67Isolate Files 68------------- 69 70These files determine which parts of the repository are transferred to the bot 71when a Swarming task is triggered. The 72[Isolate tool](https://github.com/luci/luci-py/tree/master/appengine/isolate/doc) 73hashes each file and will upload any new/changed files. Bots maintain a cache so 74that they can efficiently download only the files they don't have. 75 76 77Assets 78------ 79 80Artifacts used by the infrastructure are versioned here, along with scripts for 81recreating/uploading/downloading them. See the README in that directory for more 82information. Any time an asset used by the bots changes, you need to re-run 83gen_tasks.go. 84 85 86Tools 87----- 88 89Assorted other infrastructure-related tools, eg. isolate and CIPD binaries. 90 91 92CT 93-- 94 95Helpers for running Skia tasks in Cluster Telemetry. 96 97