commit	97537ec1d9e1be821ee309c1066dc2d9b7a5ceb0	[log] [tgz]
author	catduncan <catduncan@google.com>	Wed Dec 13 23:01:11 2023 +0000
committer	releases-prod-builder <releases-prod-builder@fuchsia-infra.iam.gserviceaccount.com>	Tue Dec 26 20:45:10 2023 +0000
tree	c2dbca0accb31adabf049646ddd8fd5b9f78c3b3
parent	923dd244f696969d80612240808fc5b56ca94810 [diff]

[checkout] Use NULL_VALUE instead of None for cached_revision

This is currently causing widespread infra failures across builders due
to an update to the data validation for buildbucket output properties.

This has been fixed at HEAD, but not on f14, and is breaking cherry-pick
attempts to f14.

Bug: 136406
Change-Id: Id7bfa9f528437eb6dd765ce876aa497f7b03ac82
Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/917202
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
Reviewed-by: Anthony Fandrianto <atyfto@google.com>
Commit-Queue: Catherine Duncan <catduncan@google.com>
Fuchsia-Auto-Submit: Catherine Duncan <catduncan@google.com>
(cherry picked from commit 47fbff24cab168e9f0cd334b12a77f2d491b6165)

210 files changed

tree: c2dbca0accb31adabf049646ddd8fd5b9f78c3b3

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