commit | 1f8bde2fe5e100cf363122b69aa96a6cc563caeb | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Thu Aug 15 17:16:57 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 15 17:16:57 2024 +0000 |
tree | d5ec585185f6ab9ebb97b7914ecb30249c2a831d | |
parent | 1623af8ccf048970fc2c67a2032d6d7c5788c070 [diff] |
submodule_roller: Move most logic to module Create a new submodule_roll recipe module and move most of the logic from the submodule_roller recipe there. Bug: b/341756093 Change-Id: I72d3392c786843053250947f45e6aaee0d5b13be Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/229717 Commit-Queue: Rob Mohr <mohrr@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Danielle Kay <danikay@google.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.