Codesign if bin/internal/release-candidate-branch.version is set

This is a narrow re-try of http://go/flutter-cl/66661, where the function added in http://go/flutter-cl/66940, which uses the existence of the file bin/internal/release-candidate-branch.version, is used to determine whether to codesign.

Also a tiny refactor, where whether to codesign is checked once outside of a loop/inner function.

In a follow-up PR I'll refactor repo_util.*release_candidate* functions, instead of doing it in this (code-sign load bearing) one.

Change-Id: I177eefd6b53add487945b6ffcc93720a26f1079e
Bug: https://github.com/flutter/flutter/issues/170561
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/66921
Commit-Queue: Matan Lurey <matanl@google.com>
Reviewed-by: Chris Bracken <cbracken@google.com>
14 files changed
tree: 0902840fd71b9b521bd2b06fb3b4cdb3307023f3
  1. .vscode/
  2. infra/
  3. recipe_modules/
  4. recipes/
  5. .gitignore
  6. .style.yapf
  7. AUTHORS
  8. CONTRIBUTING.md
  9. LICENSE
  10. OWNERS
  11. README.md
  12. recipes.py
README.md

Flutter LUCI Recipes

This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Builds can be found in the Flutter Dashboard.

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.

Contributing

Please follow instructions on Contributing docs to set up your development environment.