| commit | 4a87fc58d514382b12bbc3f4a2aff35a9fb0a28e | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Wed Sep 18 15:46:22 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 18 15:46:22 2024 +0000 |
| tree | 0d1fa773f58826c930b2e07759aced4eb3284a9e | |
| parent | 1a5a674c8dc45f659a0fb7c03a6485fc5174fc3b [diff] |
roller: Initial commit Create a new "roller" recipe module that can roll submodules, Android Repo Tool projects, CIPD packages, Bazel git_repository/git_override rules, and text files containing commit hashes. It can also copy arbitrary files from one repository to another. All of these things can be rolled individually or in one combined change (though few rolls are likely to contain all categories). It also does a couple things the previous individual rollers didn't do, like failing if run without any rolls configured in the properties, or being more explicit about status in steps. In addition, it uses the output property support added in http://fxrev.dev/1119713, and tests those properties enough that expectation files are not necessary. Bug: b/341756093 Change-Id: Ifbd33ad698280e1052d0239c03c0e2f0843a9f67 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/236263 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Reviewed-by: Ted Pudlik <tpudlik@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.