commit | 07bf19d12b18d14d3a103ded0571c703912d1fde | [log] [tgz] |
---|---|---|
author | Oliver Newman <olivernewman@google.com> | Thu Apr 28 15:39:20 2022 -0400 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 29 04:50:42 2022 +0000 |
tree | b4255fa8ba044e12ec80f09a95eb9a6caccf5f6e | |
parent | 7c111adfd36431fdc30be115cf7b693faf167947 [diff] |
checkout: Use api.git_checkout Fuchsia's `api.git.checkout()` method is being deleted and the replacement is `api.git_checkout()`, introduced in https://fxrev.dev/673645. See bug for context. Non-functional change, no expectation file differences. Bug: fuchsia:99125 Change-Id: I1745f2f1f112c332cb7b445549fc31cf315d5991 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/92720 Commit-Queue: Oliver Newman <olivernewman@google.com> Reviewed-by: 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.