| commit | e0d5a65ab39980274038a6a2ce86d49325b60c7f | [log] [tgz] |
|---|---|---|
| author | Andrii Shyshkalov <tandrii@chromium.org> | Fri Feb 22 02:53:37 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Feb 22 02:53:37 2019 |
| tree | b849c97af3d18bb221a38d89e1aa8f9a167238c3 | |
| parent | f22a7898566b18893e82d34157f66efd3985d869 [diff] |
Revert "[scheduler] Avoid copying tags or build input from the parent build" This reverts commit f22a7898566b18893e82d34157f66efd3985d869. Reason for revert: chromium recipe relied on tags_for_child_build used s.t. tester builders get displayed in console. Original change's description: > [scheduler] Avoid copying tags or build input from the parent build > > This shouldn't be needed and may be meaningless in the child build, > rather let scheduler set its own build input. > > Recipe-Nontrivial-Roll: build_limited_scripts_slave > Recipe-Nontrivial-Roll: build > Bug: 933926 > Change-Id: I98e500ae875cd89524148fe83593a40fda29f03e > Reviewed-on: https://chromium-review.googlesource.com/c/1479195 > Commit-Queue: Petr Hosek <phosek@chromium.org> > Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> > Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> TBR=phosek@chromium.org,vadimsh@chromium.org,nodir@chromium.org,tandrii@chromium.org Change-Id: I4e0212c7a548a5271912ed551fd3aa6df6e84461 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 933926 Reviewed-on: https://chromium-review.googlesource.com/c/1480748 Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Recipes are a domain-specific language (embedded in python) for specifying sequences of subprocess calls in a cross-platform and testable way.
README.md
This file!
doc/
Documentation for the recipe engine (including this file!). See the design doc for more detailed design information about the recipe engine.
infra/
Chrome infra config files.
recipes.py
The main entry point to the recipe engine. It has many subcommands and flags; run recipes.py -h to see them. Include this in your repository to start using recipes.
recipes/
Recipes in the recipe engine. These are either example recipes, or recipes which are used to test the engine (see run_test.py to see these run)
recipe_modules/
Built in recipe modules. These are very useful when writing recipes; take a look in there, and look at each of their examples subfolders to get an idea how to use them in a recipe.
recipe_engine/
The core functionality of the recipe engine. Noteworthy files include:
main.py -- The main entrypoint for the recipe engine.recipes_cfg.proto -- The protobuf file which defines the format of a recipes.cfg file.third_party/ -- third_party code which is vendored into the recipe engine.recipe_api.py -- The api exposed to a recipe module.unittests -- Unittests for the engine.There are also several files which correspond to a subcommand of recipes.py; run, and autoroll are some examples.
unittests/
Somewhat poorly named, these are higher level integration tests.
user.email and user.name are configured in git config.Run the following to setup the code review tool and create your first review:
git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools export PATH="$PATH:$HOME/src/depot_tools" git checkout -b work origin/master # hack hack git commit -a -m "This is awesome" # This will ask for your Google Account credentials. git cl upload -s -r joe@example.com # Wait for approval over email. # Click "Submit to CQ" button or ask reviewer to do it for you. # Wait for the change to be tested and landed automatically.
Use git cl help and git cl help <cmd> for more details.