firka/flutter
firka/flutter
5
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add details of how to test run a build bot change (#8734)

Browse Source 
Add the minimum set of required properties for run_recipe.py and where
to look them up.
This commit is contained in:
Chris Bracken 2017-03-13 10:14:02 -07:00 committed by GitHub
parent f075cf4450
commit 74e2243ca4
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
dev/bots/README.md
View File

@ -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/<repo> slavename=<slavename>
mastername=client.flutter buildername=<buildername>` where `<repo>` 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