commit | 9ba86f15a65a31e5aea5347120d127ddcdc7e11a | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Mon May 09 10:11:34 2022 -0700 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 09 17:24:30 2022 +0000 |
tree | 37359d10e13c3b4cf32dc17a4193a70de6ed9bd5 | |
parent | 3f9b4857973fabbee6949b7622501f4427271bb7 [diff] |
cq_label: Process a list of repos Process a list of repos instead of a host and a list of projects. This will make this recipe easier to configure in starlark. Bug: b/231587812 Change-Id: I21788256708af54a76a898903a65a5faab526d5d Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/93760 Commit-Queue: Rob Mohr <mohrr@google.com> Reviewed-by: Ted Pudlik <tpudlik@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.