Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (depot_tools, fuchsia, recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8670425659953976001 depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/20aff01e45a3a7d6a40a9e54ca66f93d1cc1761d~..94a15a0a08091d5f6c7a5e671363fb16f6358b32 20aff01 (gavinmak@google.com) Reland "Prevent argument injection in git commands and ref vali... 94a15a0 (ovsienko@google.com) ruff_chromium: port .yapfignore & CLI flags; delete _RunYapf fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/6b0504fdd61a3dbccd8d61a2cd95e6a1e9a06afb~..31ab6a4b2adce82ac7f842a57a26740c877984cd 6b0504f (etryzelaar@google.com) [rust] Optionally enable ccache usage for rust b6fa312 (carverforbes@google.com) [gce_disk_manager] Bump max retained generations to 2 04117ca (eakammer@google.com) [roller] Integrate GCS baking delay into third_party_repo_roller 31ab6a4 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/ea422e0942817baea082321e0179ff43911dbc8b ea422e0 (fancl@chromium.org) [bcid_reporter] Use cipd.ensure_tool to install snoopy_broker Please check the following references for more information: - autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller - rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback - cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md Use https://goo.gl/noib3a to file a bug. Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: If683b825e28f31378b54c6df6c7057174dbd65e0 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/479105
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.