| commit | 53624835d88622bbfc28ab90c7b822fb87efe4a3 | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@google.com> | Tue Sep 14 14:20:44 2021 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 16 04:06:24 2021 +0000 |
| tree | f87e06866966cf201d40eca3b04fc58076b00a34 | |
| parent | d9b0533bf62a1753d6ad45db28b3104f7e52797b [diff] |
Remove dependencies on fuchsia/upload module I'm splitting it up into separate modules that are specific to the upload destinations (see fxbug.dev/84596). I'll land this after the upstream CLs land, and simultaneously roll in the upstream CLs. Requires a manual roll of the fuchsia recipes repo to get up to the version at which the upload module is deleted. Bug: fuchsia:84596 Change-Id: I7a5434751dce1c2c17b6a80b850d088c9b39244c Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/60980 Pigweed-Auto-Submit: Oliver Newman <olivernewman@google.com> Reviewed-by: Rob Mohr <mohrr@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed.google.com.iam.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.