Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (fuchsia, recipe_engine) into this repository.

The build that created this CL was
https://ci.chromium.org/b/8829702415548915569

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/78a8cc96149274a7213d0b4a035daa6a3beab97d~..5a94fc3da233d3b6825c78ec74b6f70ce65ae2fd
  78a8cc9 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  0ac91d6 (gulfem@google.com)
      [ffmpeg] Include prebuilt variants in CIPD package
  68aa5db (olivernewman@google.com)
      [python3] Remove py2 support from remaining recipe modules
  9a124a6 (atyfto@google.com)
      [checkout] Respect gitiles_commit + gerrit_change w/ module flag
  ffd9c65 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  363a224 (atyfto@google.com)
      [fuchsia_roller] Add include_tryjobs option
  e986941 (olivernewman@google.com)
      [checkout] Rename incremental_build to use_incremental_cache
  bd0a024 (ihuh@google.com)
      [sdk] Upload product_bundles.json to non-platform-specific GCS...
  50c1c2e (yuanzhi@google.com)
      [femu] Remove url from cipd ref.
  c248d37 (atyfto@google.com)
      [create_branch] Add option to disable incremental builds
  5a94fc3 (olivernewman@google.com)
      [run_script] Add support for Jiri checkouts

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+log/3ac241e81e9b9a78c25d95fdfa1d3d0feb1535ff~..cb62e2ac49c58c31f7245b2e602cd21496ecc448
  3ac241e (olivernewman@google.com)
      Include log name in unknown log type error
  a92ad28 (gbeaty@chromium.org)
      Fix typo that causes failures for PY2+3 tests with --py3-only.
  0f2cbbe (zhaoyangli@chromium.org)
      Add get sub invocation api to ResultDB recipe API
  03702df (iannucci@chromium.org)
      [engine] Make step names internally coerce to `str`.
  cb62e2a (vadimsh@chromium.org)
      Add a simple `golang` recipe module.

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug.

R=tpudlik@google.com

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: Ibe1d2bef3a8c779f2382722d14a82a4cc58b384e
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/70680
Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com>
Reviewed-by: Oliver Newman <olivernewman@google.com>
1 file changed
tree: 6bbb2fae2ac51c2b4de6b077492c863ac654e54e
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. .gitignore
  6. .style.yapf
  7. cipd.ensure
  8. OWNERS
  9. presubmit.sh
  10. pyproject.toml
  11. README.md
  12. 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.