AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
2a5c66666e
skia2/infra/bots/recipe_modules
History
Mike Klein 2a5c66666e try -B 
Change-Id: I4e03d668197d76feb71113f47bae24fdd2fc6b6f
Reviewed-on: https://skia-review.googlesource.com/13334
Reviewed-by: Kevin Lubick <kjlubick@google.com>
2017-04-13 14:33:46 +00:00
..
builder_name_schema Roll recipe DEPS again 2017-02-21 15:23:11 +00:00
core Clean up no-longer-used recipes stuff 2017-04-10 14:27:58 +00:00
ct Roll Recipe DEPS 2017-02-27 14:32:26 +00:00
flavor try -B 2017-04-13 14:33:46 +00:00
infra Clean up no-longer-used recipes stuff 2017-04-10 14:27:58 +00:00
run Fix symbolization of ASAN crashes 2017-04-11 14:32:39 +00:00
swarming Manually roll recipes 2017-03-27 13:48:19 +00:00
vars Recipes: Remove depot_tools path hack 2017-04-10 16:01:46 +00:00
README.md Add/edit README files for infra/recipes 2017-04-12 16:41:01 +00:00

README.md

Skia Recipe Modules

This directory contains recipe modules designed to be used by recipes (see infra/bots/recipes). They are all Skia-specific and some are interrelated:

  • builder_name_schema - Helps to derive expected behavior from task (formerly builder) names.
  • core - Use as a starting point for most recipes: runs setup and sync steps.
  • ct - Shared Cluster Telemetry utilities.
  • flavor - Allows the caller to specify a high-level command to run, leaving the platform-specific details to be handled by the specific flavor module.
  • infra - Shared infrastructure-related utilities.
  • run - Utilities for running commands.
  • swarming - Utilities for running Swarming tasks.
  • vars - Common global variables used by Skia recipes/modules.

When you change a recipe module, you generally need to re-train the simulation test:

$ python infra/bots/recipes.py simulation_test train

Each recipe module contains a few files:

  • api.py - This is the meat of the module.
  • __init__.py - Contains a single DEPS variable, indicating the other recipe modules on which this module depends.
  • example.py - Optional, this file contains examples which demonstrate how to use the module and should contain enough tests to achieve 100% coverage for the module. The tests are run using the simulation_test command above.