Google Git
Sign in
chromium / infra / luci / recipes-py / f272cac20a48ee92ee3310aa32e9060cdd485eb9
commitf272cac20a48ee92ee3310aa32e9060cdd485eb9[log] [tgz]
authorAndrii Shyshkalov <tandrii@chromium.org>Tue Nov 21 03:35:00 2017
committerCommit Bot <commit-bot@chromium.org>Tue Nov 21 03:41:48 2017
treebb8b332fb6893b5921a2733ded14dde8fdb4c0c5
parentee90ad121c9e96935792ee2276fecc5139ddccc0 [diff]
buildbucket recipe_module: propagate is_experimental flag.

If current recipe runs as is_experimental=True, then builds triggered
should be also marked as is_experimental, unless caller opts out by
setting initializing "$recipe_engine/runtime" property.

R=iannucci@chromium.org

Bug: 786642
Change-Id: I792dae607a23ab7118e4fae6f9955950b948ab80
Reviewed-on: https://chromium-review.googlesource.com/778058
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
5 files changed
tree: bb8b332fb6893b5921a2733ded14dde8fdb4c0c5
  1. bootstrap/
  2. doc/
  3. go/
  4. infra/
  5. misc/
  6. recipe_engine/
  7. recipe_modules/
  8. recipes/
  9. unittests/
  10. .gitattributes
  11. .gitignore
  12. AUTHORS
  13. codereview.settings
  14. CONTRIBUTORS
  15. LICENSE
  16. OWNERS
  17. PRESUBMIT.py
  18. README.md
  19. README.recipes.md
  20. recipes.py
README.md

Recipes

Recipes are a domain-specific language (embedded in python) for specifying sequences of subprocess calls in a cross-platform and testable way.

Files

  • README.md

    This file!

  • bootstrap/

    Bootstrapping and vendoring related code.

  • doc/

    Documentation for the recipe engine (including this file!). Also includes doc/recipes.py, which is a file you can include in your repository to start using recipes. 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.

  • 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:

    • package.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; depgraph, run, and autoroll are some examples.

  • unittests/

    Somewhat poorly named, these are higher level integration tests.

Contributing

  • Sign the Google CLA.
  • Make sure your 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.