commit | 1867dfd2041d826d99503c3db0960ce4a4d6bced | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Mon Dec 13 08:38:38 2021 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 14 16:07:32 2021 +0000 |
tree | b0a9c191ae14c53867899703f8e81cc1202cfc18 | |
parent | 83d2d01dab9ffbcb6d41590036a36a9e3ca13eb9 [diff] |
checkout: Add option to disable branch matching Previously, if on an Android repo tool project, a CL with branch 'foo' would cause the builder to check if the manifest also had branch 'foo'. If it did, that branch would be checked out. Now, make this behavior optional. If match_branch is set, do this, otherwise just use the default branch of the manifest. Also, split logic for finding matching branches into a separate function. Change-Id: I0cf4a72714d5fe7383b750d9b0b3803f6512014c Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/73380 Reviewed-by: Oliver Newman <olivernewman@google.com> Commit-Queue: 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.