| commit | d63eb67ccf0e759735a9993af3e6a0e88dfe9282 | [log] [tgz] |
|---|---|---|
| author | Chan Li <chanli@chromium.org> | Thu Apr 14 17:13:44 2022 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 14 17:13:44 2022 |
| tree | ce16138907b5806d2502e5e6a9e03c70a86adf72 | |
| parent | 048f6f2fbb02fee8e69db6d41269c1f3b037403f [diff] |
Revert "[recipe-py] buildbucket: set `luci.buildbucket.parent_tracking` experiment according to parent" This reverts commit 048f6f2fbb02fee8e69db6d41269c1f3b037403f. Reason for revert: https://chat.google.com/room/AAAAXGgrwSo/lEUdAsRzsiE Original change's description: > [recipe-py] buildbucket: set `luci.buildbucket.parent_tracking` experiment according to parent > > This is a temporary change to make sure parent and child builds either all have the experiment on > or none of them have the experiment. This is to avoid weirdness during the experiment rollout. > > Bug: 1031205 > Change-Id: I99987e090f959f8b75d9aacd13ec5b713c00a95d > Recipe-Nontrivial-Roll: chromiumos > Recipe-Nontrivial-Roll: fuchsia > Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3584442 > Reviewed-by: Yuanjun Huang <yuanjunh@google.com> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Chan Li <chanli@chromium.org> Bug: 1031205 Change-Id: I1d5a16491338ceb3bf74810ffc7a7e70ba589bf8 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3587115 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Chan Li <chanli@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: 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.