commit	69d0426b6fad36057afbf9dcc12665b035f4dc1b	[log] [tgz]
author	Darren Chan <chandarren@google.com>	Mon Jun 24 21:04:29 2024 +0000
committer	CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com>	Mon Jun 24 21:04:29 2024 +0000
tree	18467f5b6110a04b2679eeafd1900ed762986bab
parent	0c2df4e2d2b173148b51885d6286379e395c6edc [diff]

[assembly][build] Release platform AIBs.

Allows platform AIBs to be released by using the
`platform_artifacts.json` build API module for `build`-recipe based
builders specifying `platform_artifacts_cipd_path`.

This will provide a path for deprecating
`assembly_artifacts_cipd_package`/`cipd_assembly_artifacts.json`.

Bug: 343731441
Change-Id: I4fc60d6c8fea15ae770c7a80e8a9cb10db1ed0b3
Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1069332
Reviewed-by: Oliver Newman <olivernewman@google.com>
Fuchsia-Auto-Submit: Darren Chan <chandarren@google.com>
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
Reviewed-by: Aidan Wolter <awolter@google.com>

34 files changed

tree: 18467f5b6110a04b2679eeafd1900ed762986bab

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