| commit | da369db62d9470e5bcfa5d18b39b00fdc33630b9 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Tue Sep 20 21:52:28 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 20 21:52:28 2022 +0000 |
| tree | 83337f252fd17bafae53d9f13682214186bfda10 | |
| parent | 99c3e41818598f3693646a093ad647762125c134 [diff] |
checkout: Ensure tracking is set when not rebasing Ensure the upstream tracking branch is set for changes that aren't being rebased. Change-Id: I5e1c00394f0fc45821e90935370bd47c52a8bfdb Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/111076 Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Reviewed-by: Oliver Newman <olivernewman@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed.google.com.iam.gserviceaccount.com> Reviewed-by: Oleg Filatov <olegf@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.