| commit | 2fda096eb54fcbb9aef750c3934cdbc5e4491b70 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Thu Mar 21 18:24:27 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 21 18:24:27 2024 +0000 |
| tree | 5553e00260362074a6217815e1e9e5ee92dc3dd5 | |
| parent | a09b59a962adf8a185ddf42c833df336911e9548 [diff] |
*: Switch from Path.join() to / operator The Path class in config_types will eventually be replaced with pathlib, which doesn't have a .join() method. Make an early switch to the / operator where possible. Two cases will need to use the joinpath() method, but there's no compatibility layer yet so they've been left alone. Change-Id: I17e74ed0a958d2ea23e2c1d402fc669853e088bc Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/198251 Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.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.