| commit | 6b5f34fa16f3a6ad4d1227a14d9d70532ab4d4c0 | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Wed Jun 21 21:13:49 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 21 21:13:49 2023 +0000 |
| tree | df83de21b9fcd3dc1e5de164ac5136a7b602f9b1 | |
| parent | bdd6724ac681da20ec4632b599a8f610b7215dd1 [diff] |
Update link for filing repo issues The issues of the repo tool have been migrated from Monorail into the Gerrit Tracker, hence the URL to file issues has changed. Change-Id: Ibb854017d6beec906d4cb4f928a2d27d9e3c37f6 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/152450 Commit-Queue: Rob Mohr <mohrr@google.com> Reviewed-by: Nathan Mulcahey <nmulcahey@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.