| commit | 8b4f54644f29d275e4e327eb062c31499c6d88a1 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Fri Aug 16 23:02:47 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 16 23:02:47 2024 +0000 |
| tree | 86c9d895b46ac9c19d8eec19d4e219e645d29cd6 | |
| parent | 51d7d56ccbcfcdd9b1c5a53fc68e5b1a225b8a49 [diff] |
repo_roller: Move most logic to module Create a new repo_roll recipe module and move most of the logic from the repo_roller recipe there. Many superficial changes to tests—moving them to the recipe module resulted in different step nesting. Bug: b/341756093 Change-Id: I4d9c02b5c5929f801970b6d06b3f09ebb2ec6807 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/229077 Reviewed-by: Danielle Kay <danikay@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.