| commit | a65233dc796b32fb8a540ff6983a321cb35b95ce | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Fri Sep 27 21:52:21 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 27 21:52:21 2024 +0000 |
| tree | 2c46a7f8e1aea39cb4d942027ed62960c98361e4 | |
| parent | dc51ffc1884bc7cdbddce684ab033ccdf074b8e9 [diff] |
Revert "bazel: Extract ResultStore links from Bazel output" This reverts commit 02959fa36e45c4180e0f2aaa976fbb90c0e7b8a6. Reason for revert: need stdout to be highly visible Original change's description: > bazel: Extract ResultStore links from Bazel output > > Bug: b/363338443 > Change-Id: Ie7a308b7da56d13a477454b9b20c8977a3192665 > Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/234973 > Reviewed-by: Ted Pudlik <tpudlik@google.com> > Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> > Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> > Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> > Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> # Not skipping CQ checks because original CL landed > 1 day ago. Bug: b/363338443, b/368050432 Change-Id: I706c2a34b3f2245c902523444e98dd5e40c7c53e Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/238423 Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Reviewed-by: Armando Montanez <amontanez@google.com> Commit-Queue: Rob Mohr <mohrr@google.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.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.