Google Git
Sign in
pigweed / infra / recipes / 65e1baf9e8f5f65d3dd39c547cb38b2b043d79fe
commit65e1baf9e8f5f65d3dd39c547cb38b2b043d79fe[log] [tgz]
authorRob Mohr <mohrr@google.com>Mon Aug 12 23:17:21 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Aug 12 23:17:21 2024 +0000
treea631a8353aba6d17ec33b7b0d4f644d12d9e0f22
parent6a592ed4ed08c892f9c494c7667f106ed549b6e0 [diff]
repo_roller: Move repo-specific parts to function

Move the repo-specific parts of the repo_roller recipe to a function.
This is a step towards making the RunSteps() functions in each roller
look more or less the same, so they can be merged in the future.

No changes to expectation files.

Bug: b/341756093
Change-Id: I38333a3d70a36d75b168a133a4c26e1c507ed2cc
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/229075
Reviewed-by: Danielle Kay <danikay@google.com>
Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com>
Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: a631a8353aba6d17ec33b7b0d4f644d12d9e0f22
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. black ⇨ .cipd/black
  6. .editorconfig
  7. .gitignore
  8. .style.yapf
  9. AUTHORS
  10. cipd.ensure
  11. LICENSE
  12. OWNERS
  13. presubmit.sh
  14. pyproject.toml
  15. README.md
  16. recipes.py
README.md

Pigweed Recipes

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.

Getting the Code

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

Running Tests

./presubmit.sh runs three different sets of tests:

  • Recipe expectation tests (./recipes.py test train)
  • Formatting (./black --diff --check .)
  • Dependencies (.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.