commit | c88b237379af1d562d73c01c163fc1ae6a6e1921 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Fri Nov 12 09:46:45 2021 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Nov 12 18:41:37 2021 +0000 |
tree | f05b2d12de6e40f60877a4631e92b3ae7fd8e65e | |
parent | 25b177cfceaa3567b92a35b4beac4cbc7a6e33cd [diff] |
target_to_cipd: Enable using pw_presubmit Enable using the pw_presubmit recipe module in target_to_cipd in place of the build recipe module. This should enable moving the logic around which files get selected and any renames done to those files from the LUCI config to the project git repository. Bug: 523 Change-Id: I421623cf6d20c7cb60452f4af747ae6fc8e6dd8d Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/67230 Reviewed-by: Ted Pudlik <tpudlik@google.com> Commit-Queue: 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.