| commit | 7122c4541287cb0b9b8a40a5bf6422c73020408d | [log] [tgz] |
|---|---|---|
| author | Greg Edelston <gredelston@google.com> | Tue Mar 21 17:32:31 2023 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 21 17:32:31 2023 |
| tree | 75eb815d9a46b689f1c2c64068c207f4168c7c7a | |
| parent | 5bea4e79788afea5b1b2176b2da054c5a1340ce1 [diff] |
Fix typo about step_test_data As far as I can tell, step_test_data should be a callable. At least, that's how it's always used in the recipe engine. I think it would be helpful for this section to include more info about the difference between output, output_text, output_stream, etc., but I don't understand that difference well enough to document it. BUG=None TEST=None Change-Id: If91c38bffad646b8f349966d67ae8aacffe034e8 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/4342435 Auto-Submit: Greg Edelston <gredelston@google.com> 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.