| commit | 5bdad0203b51505ce2699dba8027edfd83e5909b | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Tue Jul 18 21:15:44 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 18 21:15:44 2023 +0000 |
| tree | 790b1e6fac8a30f1b0a73db3a2fd76dfa5a4733d | |
| parent | ccd4915c0fb0eefa2f1e9304743f0b2be5ea28f3 [diff] |
rerunner: Use luci-scheduler to launch builds Use luci-scheduler instead of buildbucket to launch builds. This will limit most builders to at most one concurrent build since luci-scheduler manages concurrency and buildbucket does not. Bug: b/288464961 Change-Id: I1006553167759fd112224dcfb527ee0a5c6f5c25 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/156790 Commit-Queue: Rob Mohr <mohrr@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Oliver Newman <olivernewman@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.