Reland "[run_script] Stop using api.python()"

This reverts commit 3733f83f5a9ecdeb73de5f8ce924bd68d6eb4982.

Reason for revert: relanding after fixing the firmware repo to always
use the correct vpython spec for all scripts.

Original change's description:
> Revert "[run_script] Stop using api.python()"
>
> This reverts commit e0c129d2aee1e23f2e8a8767e99fc8b2820bc435.
>
> Reason for revert: Broke the firmware builders :(
> https://ci.chromium.org/b/8828825951656567969
> Seems like the Python script invokes a tree of python subprocesses
> and they all implicitly rely on vpython. I'll look into fixing that 
> next week.
>
> Original change's description:
> > [run_script] Stop using api.python()
> >
> > If a script relies on vpython then it should explicitly use a vpython
> > shebang, which will keep this recipe simple and also help with locally
> > reproducing builds since infra won't hold the script differently than a
> > local developer would.
> >
> > The only builders that rely on this feature are the firmware builders,
> > so before I land this I'll send changes to update those builders'
> > scripts to use vpython shebangs.
> >
> > Bug: 89307
> > Change-Id: I71f48db5b84f52ead4c3713d61abeff54fb44040
> > Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/610781
> > Reviewed-by: Anthony Fandrianto <atyfto@google.com>
> > Commit-Queue: Oliver Newman <olivernewman@google.com>
>
> Bug: 89307
> Change-Id: I97b7dfd45ceda94dbc0b346dd542f4993dd99455
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/613969
> Reviewed-by: RubberStamper 🤖 <android-build-ayeaye@system.gserviceaccount.com>
> Commit-Queue: Oliver Newman <olivernewman@google.com>

Bug: 89307
Change-Id: I21dc65ac5f688e624566bb5f7e042db9e84500b0
Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/614861
Reviewed-by: RubberStamper 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Reviewed-by: Anthony Fandrianto <atyfto@google.com>
Commit-Queue: Oliver Newman <olivernewman@google.com>
2 files changed
tree: ecc24e08b13914645df7868a611aa9bc877f44a9
  1. git-hooks/
  2. infra/
  3. manifest/
  4. recipe_modules/
  5. recipe_proto/
  6. recipes/
  7. scripts/
  8. .editorconfig
  9. .git-blame-ignore-revs
  10. .gitignore
  11. AUTHORS
  12. CRITICAL_OWNERS
  13. LICENSE
  14. OWNERS
  15. PATENTS
  16. pyproject.toml
  17. README.md
  18. recipes.py
README.md

Fuchsia Recipes

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.

Getting the code and setting up your environment

For everyday development

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.

Quick changes

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.

Code formatting

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.
    },
    ...
}