| commit | 634733f84a86c1e4934cb462cff5aedafe078a13 | [log] [tgz] |
|---|---|---|
| author | slliu <slliu@google.com> | Thu Apr 11 01:53:36 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 11 01:53:36 2024 +0000 |
| tree | 12977124c8d83b8147a15b8f1d8aec8f6bb550ec | |
| parent | cb3fa8b87898db56c8bf0d91af4b524eac283456 [diff] |
multi_roller: Initial commit The multi_roller recipe launches and synchronizes multiple rollers. The rollers to launch is specified via the input properties. The recipe will use the subbuild recipe_module to launch the rollers. Once each roller has created a roll CL, it will also output a property that exposes the gerrit host and change-id of that roll CL. The rollers will then wait for a Rolls-Synced label. Multi_roller watches over all the rollers and only sets the Rolls-Synced label on each roll CL once all of the roll CLs pass presubmit checks. Bug: b/324426822 Change-Id: I1b37ce6bf010cf7e0b6aae2181a3fe13370330cb Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/194150 Reviewed-by: Rob Mohr <mohrr@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: Samuel Liu <slliu@google.com> Pigweed-Auto-Submit: Samuel Liu <slliu@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.