| commit | c78a7300e1fe399a2af8ab2e6b0691d40e6c1258 | [log] [tgz] |
|---|---|---|
| author | Ina Huh <ihuh@google.com> | Tue Apr 02 22:25:52 2024 +0000 |
| committer | Ina Huh <ihuh@google.com> | Tue Apr 02 22:25:52 2024 +0000 |
| tree | cdc9405f9b8411d2e02c629233af8bda94722f11 | |
| parent | be0dcec52c419b796298324c97599ea27f8a7b4e [diff] |
Revert "[checkout] Fix check for is_manifest_commit." This reverts commit a4bf90bef0798d66199e36058463e799afd99edf. Reason for revert: b/332591594 Original change's description: > [checkout] Fix check for is_manifest_commit. > > The check only checked that the commit project was the same as the > remote project, but if the host is different, then the checkout would > fail because it's looking for the commit id of a different repo. Instead > we should just compare the remote and commit_remote. This only affects > builds without a triggering commit or gerrit change (like led jobs) > which rely on recipe_wrapper to populate the gitiles commit with a > revision from the default public integration repo, which wouldn't work > for internal builders. > > Bug: 42073261 > Change-Id: I3d6e05f2720e40accb2ead4928fdb1642359d443 > Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1017160 > Fuchsia-Auto-Submit: Ina Huh <ihuh@google.com> > Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com> > Reviewed-by: Oliver Newman <olivernewman@google.com> Bug: 42073261 Change-Id: Ieb45c6fca8167b312cbb151c52713eed104f1c52 Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1019452 Reviewed-by: RubberStamper 🤖 <android-build-ayeaye@system.gserviceaccount.com> Reviewed-by: Oliver Newman <olivernewman@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. }, ... }