| commit | 993706de63d7d4deab2025d7719974aad7e5619c | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Thu Jan 13 06:52:19 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 13 08:04:18 2022 +0000 |
| tree | 04480b97f2688e080167efe9e23af166553e878f | |
| parent | b10bcc658495daf6de92da8b627b9159d395660d [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/8825172570525562561 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/0b5813d0fc372f686b9a9ab80e9b9460f862002e~..364d75b0f4c208aba9463e63f04d7e136e3374e1 0b5813d (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 9052739 (nmulcahey@google.com) [codesearch] Fix module update ordering 364d75b (nmulcahey@google.com) [codesearch] Push if any changes recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/ffb8f400af94e1955236df9e30c153729173fa2e ffb8f40 (bryner@google.com) Add zstandard extraction to archive recipe module. 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 Bugdroid-Send-Email: False Change-Id: Ib7a95c11a746638c056b7d795c924b3d032944a2 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/78520 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Commit-Queue: 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.