[buildbucket] Make default git_ref consistent

It's 'refs/heads/main' for `try_build_message()` but 'refs/heads/master'
for `ci_build_message()`. This is an unnecessary discrepancy, and seeing
as "main" is the preferred primary branch name now, it makes sense to
standardize around "main".

Recipe-Nontrivial-Roll: build
Recipe-Nontrivial-Roll: build_limited_scripts_slave
Recipe-Nontrivial-Roll: chrome_release
Recipe-Nontrivial-Roll: chromiumos
Recipe-Nontrivial-Roll: depot_tools
Recipe-Nontrivial-Roll: fuchsia
Recipe-Nontrivial-Roll: infra
Change-Id: I1bb90f2e92644ec2432455174214542a6c7cceb0
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2885818
Auto-Submit: Oliver Newman <olivernewman@google.com>
Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
10 files changed
tree: df67f8ae0a9833092b33e7ae584dcd26dcdaa1fa
  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. .vpython3
  14. AUTHORS
  15. codereview.settings
  16. CONTRIBUTORS
  17. LICENSE
  18. OWNERS
  19. PRESUBMIT.py
  20. README.md
  21. README.recipes.md
  22. 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.