From 74e2243ca4423a51c9a60ff9968280f02df2b91b Mon Sep 17 00:00:00 2001 From: Chris Bracken Date: Mon, 13 Mar 2017 10:14:02 -0700 Subject: [PATCH] Add details of how to test run a build bot change (#8734) Add the minimum set of required properties for run_recipe.py and where to look them up. --- dev/bots/README.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/dev/bots/README.md b/dev/bots/README.md index 3d3fa7901c8..0925f481b7c 100644 --- a/dev/bots/README.md +++ b/dev/bots/README.md @@ -59,10 +59,17 @@ by the [luci/recipes-py github project](https://github.com/luci/recipes-py). The typical cycle for editing a recipe is: -1. Make your edits (probably to files in `//chrome_infra/build/scripts/slave/recipes/flutter`). -2. Run `build/scripts/slave/recipes.py simulation_test train flutter` to update expected files (remove the flutter if you need to do a global update). -3. Run `build/scripts/tools/run_recipe.py flutter/flutter` (or flutter/engine) if something was strange during training and you need to run it locally. -4. Upload the patch (`git commit`, `git cl upload`) and send it to someone in the `recipes/flutter/OWNERS` file for review. +1. Make your edits (probably to files in + `//chrome_infra/build/scripts/slave/recipes/flutter`). +2. Run `build/scripts/slave/recipes.py simulation_test train flutter` to update + expected files (remove the flutter if you need to do a global update). +3. Run `build/scripts/tools/run_recipe.py flutter/ slavename= + mastername=client.flutter buildername=` where `` is one + of `flutter` or `engine`, and `slavename` and `buildername` can be looked up + from the *Build Properties* section of a [recent + build](https://build.chromium.org/p/client.flutter/one_line_per_build). +4. Upload the patch (`git commit`, `git cl upload`) and send it to someone in + the `recipes/flutter/OWNERS` file for review. ## Editing the client.flutter buildbot master