| commit | 1e134db860001a81b37cd0e617c19a7cab2e5893 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Mon Sep 30 17:48:02 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 30 17:48:02 2024 +0000 |
| tree | 9feeda1384498ca08ce3162692547c5616a74cc1 | |
| parent | fe7863291fa38652047b1c39e106a83710862cee [diff] |
bazel_roll: Relocate functionality from bazel mod Move code from the bazel module to the bazel_roll module, specifically the code dealing with updating bazel module pins. This means the checkout module will now depend on the bazel_roll module instead of the bazel module, so changes to bazel build logic will only require running Bazel builders in recipe testing, and not all builders. Change-Id: I7bad503921846b61b74991707ec6c57545ccba4a Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/238832 Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Reviewed-by: Ted Pudlik <tpudlik@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.