commit | 60e4c0daf17419e102636f2cbd8807e2e2a9860e | [log] [tgz] |
---|---|---|
author | Ina Huh <ihuh@google.com> | Mon Apr 22 19:38:13 2024 +0000 |
committer | CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 22 19:38:13 2024 +0000 |
tree | 9939fe52cef541c1925959ed54889f7ad26d1cda | |
parent | 4a83dda12043b984ad5d226e6df7389348669a2f [diff] |
[build] Notify when builder did not rebase change if failures occur. Since integration is checked out at HEAD but only the patch is not rebased when `do_not_rebase_patch` is true, build/test failures can occur if the patch is out-of-date with the rest of integration. This may not be a problem with the CL itself and just needs the CL to be rebased on top of HEAD so mention that in the failure summary. Bug: 335727014 Change-Id: If6b1fe710c5337e38f6c4fcecabb20e66566ac85 Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1032020 Reviewed-by: Oliver Newman <olivernewman@google.com> Fuchsia-Auto-Submit: Ina Huh <ihuh@google.com> Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
This repository contains recipes for Fuchsia.
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 Fuchsia 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 Fuchsia in your local environment.
See go/fuchsia-recipe-docs for complete documentation and a guide for getting started with writing recipes.
The recommended way to get the source code is with jiri. A recipe will not run without vpython
and cipd
, and using these recommended jiri manifests will ensure that you have these tools.
You can use the fuchsia infra Jiri manifest or the internal version (Googlers-only). Once that manifest is imported in your local jiri manifest, jiri update
should download vpython
and cipd
into <JIRI ROOT>/fuchsia-infra/prebuilt/tools/
. If you add that directory to your PATH, you should be good to go.
If you're just trying to make a single small change to in this repository and already have your local environment set up for recipe development (e.g. because you work with another recipes repository) you can simply clone this repository with git:
git clone https://fuchsia.googlesource.com/infra/recipes
Then it will be up to you to ensure that vpython
and cipd
are available in your PATH.
We format python code using Black, an open-source Python autoformatter. It should be in your PATH if you followed the instructions for setting up your environment.
After committing recipe changes, you can format the files in your commit by running black .
in your project root.
Many editors also have a setting to run Black automatically whenever you save a Python file (or on a keyboard shortcut). For VS Code, add the following to your workspace settings.json
to make your editor compatible with Black and turn on auto-formatting on save:
{ "python.formatting.provider": "black", "python.formatting.blackPath": "<absolute path to the black executable>", "[python]": { "editor.formatOnSave": true, "editor.rulers": [88], // Black enforces a line length of 88 characters. }, ... }