[python3] Mark remaining modules as py3-compatible

Mostly by using `api.file.read_proto()` to deserialize jsonpb files,
because it sorts keys, whereas using `api.file.read_text()` and then
`json_format.Parse()` doesn't sort keys, resulting in different key
orders between Python 2 and 3.

Also use `api.raw_io.output_text()` instead of `api.raw_io.output()`,
because `output()` returns a bytes object in Python 3, whereas
`output_text` returns a string in both Python 2 and Python 3.

Change-Id: Ia0e9ed076edfb3340c091db1ed75d9c2b9d57e4c
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/18520
Commit-Queue: Oliver Newman <olivernewman@google.com>
Reviewed-by: Godofredo Contreras <godofredoc@google.com>
Reviewed-by: Rob Mohr <mohrr@google.com>
22 files changed
tree: e80847158e70c3b4da280f9e31d253f84836aba3
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. .gitignore
  5. .style.yapf
  6. AUTHORS
  7. branch_recipes.py
  8. LICENSE
  9. OWNERS
  10. README.md
  11. recipes.py
README.md

Flutter LUCI Recipes

This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Actual builds can be seen at ci.chromium.org.

Supported repositories roll their .ci.yaml into flutter/infra, which updates what properties builds have. For example, flutter config specifies various dependencies the different tests require, which are then used by the flutter_deps recipe_module No modifications to flutter/infra are required to work on the recipes.

Configuration

Tricium configurations recipes repo.

Recipe Branching for Releases

The script branch_recipes.py is used to generate new copies of the LUCI recipes for a beta release. See Recipe Branching for Releases for more information. For usage:

$ ./branch_recipes.py --help