| commit | db324826f7bd8bf77d0274b6c3a03ca0e7597973 | [log] [tgz] |
|---|---|---|
| author | Ina Huh <ihuh@google.com> | Fri May 03 18:28:44 2024 +0000 |
| committer | CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 03 18:28:44 2024 +0000 |
| tree | f0ebd8278e936381c206d75ed0880e241430c468 | |
| parent | 30b48c01bab7486d0a43dfcf34e6925e402d9ae7 [diff] |
[tree_status] Support using new tree status app. This causes the tree-closer to update both the old and new tree status apps, but uses the old status app as the source of truth for getting the current tree status. Once the tree_name property is provided, the tree-closer will start using the new app as the source of truth, but until the Gerrit plugin and CV are migrated to using the new status app, we'll have to keep both in sync, so any manually set statuses in either app will be copied over to the other if detected by the tree-closer, and the auto-submit builder will check both and take the latest status. Bug: 332741591 Change-Id: Icdf7f72a2b8ab933d99d5aa2336722e3bc8bf128 Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1041743 Reviewed-by: Oliver Newman <olivernewman@google.com> Fuchsia-Auto-Submit: Ina Huh <ihuh@google.com> Commit-Queue: Ina Huh <ihuh@google.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. }, ... }