| commit | e97af0efb1de1c6f7218bafb777f7eaef9ec8247 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue Mar 22 06:51:27 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 22 18:30:02 2022 +0000 |
| tree | 2a3150142c182e5424fd11cd69d74328e4541512 | |
| parent | 7d2f42ec900ec6753a5ddb9f63eb68a2d837407b [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/8819011976756760881 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/bd1a3f3cc651a3ff08817817bd556f1ba9eb644f~..a84d335d8deade13e89b0a8d803a9fa17c71c03d bd1a3f3 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 06d59de (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 6dce105 (haowei@google.com) [git] Allow git.log() API to output commit hashes only a84d335 (ihuh@google.com) [testing_requests] Enable ffx for emu only. recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/3db9e1bd1e7a415358105a5018358bd43031fd6b 3db9e1b (chanli@chromium.org) Reland "[recipe-py] buildbucket: enable buildbucket tracking pa... More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=mohrr@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Ib73e5c1b32503834d0aee4c270d9096ea603df6b Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/88716 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Reviewed-by: Rob Mohr <mohrr@google.com> Commit-Queue: Rob Mohr <mohrr@google.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.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.