| commit | aaece40ab207cf7c6ea5a2c645579e92cf071383 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Sat Aug 10 02:00:35 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Aug 10 02:00:35 2024 +0000 |
| tree | f790052bdab521c3a1846277f0a82eb962ade25d | |
| parent | c09a5799b7145ee194fa91c9ec531cff584b0d5b [diff] |
cipd_roller: Move logic to module Create a new cipd_roll recipe module and move most of the logic from the cipd_roller recipe there. This is the first step in making a roller recipe that can roll .bazelversion files, CIPD packages, submodules, etc. together. No changes to logic, only moving code around. Bug: b/341756093 Change-Id: I11451e24989ca2ed02212c1f5bf7b55d638b30f7 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/228653 Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Reviewed-by: Oliver Newman <olivernewman@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.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.