| commit | efffe69cdac42f94b8409ecdc272231f59cd4e3c | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Thu Dec 02 00:06:37 2021 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 02 00:37:47 2021 +0000 |
| tree | 5fb37b4583fdcf41aeabeaea4f0fd4facf3d05ce | |
| parent | c866c340b705ef43c0b548009fe55326ee321307 [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/8829003412680968977 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+/91e75749464d20e5e032506d27908a67224c2acf 91e7574 (rudymathu@google.com) [recipes] Emit cached revision as an output property recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/6ea35fceeb7a5bf0513018059ef9b09c39c79400~..346c0ea55f67794598b8e5b264411c05ed565918 6ea35fc (iannucci@chromium.org) Recipe 'run' command has a weirdo concept of how working directory df92157 (vadimsh@chromium.org) Add a simple `nodejs` recipe module. 346c0ea (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from e4c95e4e4cdc to 05791e01bd94 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: I42142ee1a01bccd771833bc4aefd20c7351dd0f0 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/71662 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> 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.