| commit | 8ad34f8548854f0cbdfff61c700311e27dc4c47e | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Mon Nov 04 19:25:51 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Nov 04 19:25:51 2024 +0000 |
| tree | bac909500c5f83ae4c0e11f3c798ad37c44e66f7 | |
| parent | 639cb6c41312028fd4ed83d737e049e728596595 [diff] |
bazel_roll: Make roller code more flexible Don't add any features for rolling anything but git_repository and git_override rules, but change the code that does roll them to not be so tied to exactly those rules and their arguments. Bug: b/376915917 Change-Id: Ic4a6281cea3b376f69e7c25e7c92dc8b9a9c4b17 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/246392 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Reviewed-by: Taylor Cramer <cramertj@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.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.