| commit | 1fe880ac1b442611e1bb7d809a18ad90592c254f | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue May 03 16:58:48 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 03 17:36:45 2022 +0000 |
| tree | 342f0faae1f9b3265d83a88d531a5389b2f72c51 | |
| parent | 71bb6452e140c9eeaec6f83ce3ae3d11a267a87c [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (fuchsia, recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8815168689083489313 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/fe38e21c4f4399ae2b465d80303fc6c1543a5892~..6dbbd36979c6bc6489d041f0082b6bbea01f44cb fe38e21 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 6dbbd36 (olivernewman@google.com) [fuchsia] Fix release version comparison recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/82fb654d0e289ca7f72aa4e57fc437f4877d42e7 82fb654 (meiring@google.com) [recipes-py] Update ResultDB exoneration example to populate re... More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=tpudlik@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I6a7d2d08d5b90a9a60a9ac6b9637cd8cdf9c4e01 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/93520 Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com>
This repository contains recipes for Pigweed.
A recipe is a Python script that runs a series of commands, using the recipe engine framework from the LUCI project. We use recipes to automatically check out, build, and test Pigweed and downstream projects using Pigweed in continuous integration jobs. The commands the recipes use are very similar to the ones you would use as a developer to check out, build, and test Pigweed in your local environment.
See go/pigweed-recipe-docs for complete documentation and a guide for getting started with writing recipes.
The recommended way to get the source code is with git.
git clone https://pigweed.googlesource.com/infra/recipes
In most cases you will need a Chromium depot_tools checkout in your PATH as well.
git clone https://chromium.googlesource.com/chromium/tools/depot_tools ~/depot_tools echo 'export PATH="$PATH:$HOME/depot_tools"' >> ~/.bashrc
./presubmit.sh runs three different sets of tests:
./recipes.py test train)./black --diff --check .).recipe_deps/fuchsia/scripts/cleanup_deps.py --check)The formatting check will tell you what‘s wrong but not fix it. For that you need to run ./black .. Similarly, the dependencies check will tell you what’s wrong but you'll need to edit the files to fix issues.
If not using ./presubmit.sh you'll need to run ./scripts/ensure_black.sh before ./black is present.