[buildbucket] Expose DEFAULT_FIELDS

Whenever a downstream project needs a build field returned that's not in
the default fields, it requires listing out all the other required
fields as well, even if they're in the defaults, because the default
fields are overridden by the `fields` argument.

To address this, expose the default fields as the
`api.buildbucket.DEFAULT_FIELDS` property so that downstream repos can
easily request extra fields while still getting all the default ones.
For example:

  fields = {'infra.recipe'}.union(api.buildbucket.DEFAULT_FIELDS)
  api.buildbucket.search(..., fields=fields)

Recipe-Nontrivial-Roll: build_limited_scripts_slave
Recipe-Nontrivial-Roll: fuchsia
Change-Id: Id79becafe4b3fc7358e04bc5736080be14e8983f
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1918689
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
Commit-Queue: Oliver Newman <olivernewman@google.com>
5 files changed
tree: 24a00fe36c92a2645ec9d23dd9fdc5b8c6db18f8
  1. doc/
  2. infra/
  3. misc/
  4. recipe_engine/
  5. recipe_modules/
  6. recipe_proto/
  7. recipes/
  8. unittests/
  9. .gitattributes
  10. .gitignore
  11. .style.yapf
  12. .vpython
  13. AUTHORS
  14. codereview.settings
  15. CONTRIBUTORS
  16. LICENSE
  17. OWNERS
  18. PRESUBMIT.py
  19. README.md
  20. README.recipes.md
  21. 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.

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.

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:

# 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.