| commit | 43c669b6bebd196d6027a9821a7eb86ab882cfcf | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Mon Jan 10 12:44:04 2022 -0800 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 10 21:27:23 2022 +0000 |
| tree | b2657e853d9e9e101fe01cf4ede078f28c3458cd | |
| parent | f1c573f10d0dd6cf534c830f895f2d8acb55dbf5 [diff] |
(repo|submodule|txt)_roller: Attribute rolls For single-commit rolls attribute rolls to the original commit author. Hide this behind a property since the permissions may not be set up on all necessary gerrit hosts. Added code to keep track of author, owner, and reviewer names as well as email addresses, so the name can be used in the attribution as well. Changed testing code to use the same account for both author and owner in most cases, since the attribution code wouldn't be used if they differ. It's possible something relating to one of those and not the other could regress since they're no longer independently tested, but unlikely. Bug: 595 Change-Id: I720b33d9b994bba7b9427b8e64cd21dbf4bb7e4b Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/77760 Reviewed-by: Anthony Fandrianto <atyfto@google.com> Commit-Queue: 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.