commit | 9437c958bbdd1c36cdf30996037243048d6a826c | [log] [tgz] |
---|---|---|
author | Yuanjun Huang <yuanjunh@google.com> | Thu Jun 04 21:54:53 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 04 21:54:53 2020 |
tree | 41f7543c6869cc0b21731945fbcc25e2d47d5bb6 | |
parent | ba2e549fc2f9cc837deb0a69789067c74021e38e [diff] |
Parse tags from output prop and set into build.proto for bbagent Extract the tags from output properties and set them into build.proto to send to bbagent if users set tags during runtime. Related CL about adding the UpdateMask path: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/2229409 This change has been tested via a Led job by changing a recipe to call hide_current_build_in_gerrit api and pointing to this local recipe engine. The tag can be successfully added. https://chromium-swarm.appspot.com/task?id=4c946688510e6d10 Bug:1040685 Change-Id: I0cbfcf506e3739a903e0fff3c17053dfac466dba Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2225937 Commit-Queue: Yuanjun Huang <yuanjunh@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.