| commit | 086f88d1b582dd442d3469055ca92b907bb33f7d | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Thu Jan 11 21:22:30 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 11 21:22:30 2024 +0000 |
| tree | 9e16761f2f320fd5730fc8087b50303588d2c614 | |
| parent | eb705be7c18ee3f6b9f0d263ae5de3f7d1b5b279 [diff] |
Revert "checkout: Save git config if checkout fails" This reverts commit eb705be7c18ee3f6b9f0d263ae5de3f7d1b5b279. Reason for revert: this doesn't actually help because the cache directory is purged when commands fail Original change's description: > checkout: Save git config if checkout fails > > Bug: b/314378562 > Change-Id: Ic8f5c101c3a173dd15a0fa15861574af1b31f610 > Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/187470 > Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> > Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> > Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> > Reviewed-by: Ted Pudlik <tpudlik@google.com> TBR=mohrr@google.com,pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com,tpudlik@google.com,auto-submit@pigweed-service-accounts.iam.gserviceaccount.com Change-Id: Ib364ecd0fd21dc8bfb38ccd5d48388112d23e7e7 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: b/314378562 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/187452 Reviewed-by: Ted Pudlik <tpudlik@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@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.