| commit | 0f2e60c02d24bd13a434fca5027fdc617a66b186 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Mon Jun 10 16:40:32 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 10 16:40:32 2024 +0000 |
| tree | 93b52917d05bf2881e8537f5666f26beaf35e10e | |
| parent | 74e845828ba3ce06f1ecb0d600a57c93b8f6d35b [diff] |
bazel: Update remote when applying a pending change When a pending change on repository A is applied to a WORKSPACE file referencing repository B, and repositories A and B are "equivalent", then we need to also update the remote to point to repository A. Only submitted changes are mirrored between repositories, so the pending change on A is not visible on B until it's submitted. Bug: b/275107504 Change-Id: Ic46e02ecab95bf6641035aeab2e168b2f59d77fb Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/215211 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Ted Pudlik <tpudlik@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.