roll: recipes/shac.resources/cipd.ensure, recipes/shac.resources/cipd.resolved

recipes/shac.resources/cipd.ensure

recipes/shac.resources/cipd.resolved

Roll-Count: 2
Roller-URL: https://cr-buildbucket.appspot.com/build/8670011458440053329
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I83d97b9d64d831ff52791f1274d4521b6e47e524
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/482085
2 files changed
tree: 4de1ab03bdddb4d89b1fe8d2b714f0766e13f2bc
  1. .agents/
  2. infra/
  3. recipe_modules/
  4. recipe_proto/
  5. recipes/
  6. scripts/
  7. .aiderignore
  8. .editorconfig
  9. .gitignore
  10. .style.yapf
  11. AUTHORS
  12. GEMINI.md
  13. LICENSE
  14. OWNERS
  15. presubmit.sh
  16. pyproject.toml
  17. README.md
  18. recipes.py
  19. ROLLER_OWNERS
  20. shac.ensure
  21. shac.star
  22. shac.textproto
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.