commit | 0e4ad7bf162bfd36d111e475c75763b1d8c25c7a | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@chromium.org> | Tue Oct 13 22:45:01 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 13 22:45:01 2020 |
tree | d33f14b3363917657aa4fdb721d866fe7a227c82 | |
parent | 01b9c522df32a1f5d0dbb31e0b86bd22e3085bf1 [diff] |
Add swarming_task_url property to LedLaunchData. Adding a property with the swarming_task_url saves callers from having to manually construct the url or extract it from the presentation of the created step, which would rely on the implementation details of the link with the specific name being created on the last step that was run. Change-Id: Iae2897ea8f97762c4083309eae247d069e8379b6 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2469296 Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@google.com> Commit-Queue: Andrii Shyshkalov <tandrii@google.com>
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.