commit | 56ff5e8a78cfb14076273f06f663c9a59faf68d0 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Wed Nov 13 17:43:09 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 13 17:43:09 2024 +0000 |
tree | 37195a20b9b838bd2ff3d49753e1dd700d111566 | |
parent | a9ad3b89293326ab4c660b0b12c36e086ca22157 [diff] |
cipd_roll: Split update_package() Split update_package() into two separate methods. The new update_package() reads the JSON file, calls select_version() to get the new version, then writes the JSON file. Also, we don't use "cp38" and similar strings as platforms, so remove support for them. Bug: b/376915917 Change-Id: I384baf4b7f1e3866d16d5c344e8e49be9a0e0dc8 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/248576 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: Rob Mohr <mohrr@google.com> Reviewed-by: Oliver Newman <olivernewman@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.