| commit | 5dd297c49451f92e4b0ab9302e7fdb8312ff84bd | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Mon Aug 19 16:43:24 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 19 16:43:24 2024 +0000 |
| tree | a308c51089da4484afc0b346e38d5ae54fa956fe | |
| parent | 17a0aa82a96ea89507257d7fd458d952ad74c4fa [diff] |
bazel_roller: Move Bazel-specific parts to module Move the Bazel-specific parts of the bazel_roller recipe to a new module, bazel_roll. Not putting this in the pre-existing bazel module since we shouldn't have to test all Bazel-based builders when modifying Bazel roller logic. Leaving api.bazel.update_commit_hash() in the bazel module because it's tightly coupled with api.path.retrieve_git_repository_attributes() which is also used by the checkout module. Bug: b/341756093 Change-Id: Ibdc1cc85e2d0dcee24e26d5137f8fcc0d107a44b Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/230293 Reviewed-by: Danielle Kay <danikay@google.com> Commit-Queue: Danielle Kay <danikay@google.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.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.