| commit | ee828f03fefb220251ed066a9e55bd652385ed90 | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@google.com> | Fri Jun 19 17:01:33 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 19 17:01:33 2020 |
| tree | 68f2993f41602cf29701ac92d2f638a34e7dde8b | |
| parent | 7ad18cd7034574b040416175413d15652b82f10e [diff] |
[cmd] Add "dump_specs" command
The new `./recipes.py dump_specs` will print out the repo's
dependencies' recipes.cfg files to stdout. The output is a JSON object
mapping repo names to specs, of the form of the new
recipes_cfg.DepRepoSpecs protobuf:
{
"repo_specs" {
"fuchsia": {
"api_version": 2,
"autoroll_recipe_options": {
...
},
},
"recipe_engine": {
"api_version": 2,
...
}
}
}
Bug: fuchsia:54380
Change-Id: Iaf8d7a2dd0ed2020142a7030258a795edafa5c8e
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2252547
Commit-Queue: Oliver Newman <olivernewman@google.com>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Recipes are a domain-specific language (embedded in python) for specifying sequences of subprocess calls in a cross-platform and testable way.
They allow writing build flows which integrate with the rest of LUCI.
Documentation for the recipe engine (including this file!). Take a look at the user guide for some hints on how to get started. See the implementation details doc for more detailed implementation information about the recipe engine.
user.email and user.name are configured in git config.Run the following to setup the code review tool and create your first review:
# Get `depot_tools` in $PATH if you don't have it git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools export PATH="$PATH:$HOME/src/depot_tools" # Check out the recipe engine repo git clone https://chromium.googlesource.com/infra/luci/recipes-py $HOME/src/recipes-py # make your change cd $HOME/src/recipes-py git new-branch cool_feature # 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.