| commit | 93c8ef9d56bbc4ff7337339f06d4e83fb2f26ba6 | [log] [tgz] |
|---|---|---|
| author | Christopher Fujino <fujino@google.com> | Mon Jul 01 20:45:26 2024 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 01 20:45:26 2024 +0000 |
| tree | 25778d54d3994c24bb10cefc84d1bf07e9856996 | |
| parent | fa32b5d1fc9af4ff8c86e06f48e728d37db425e3 [diff] |
Support new Apple Certificate in codesigning Cherry picks the following CLs that were made against the flutter-3.18-candidate.18 branch in order to run test release builds to verify the correctness (since codesigning has to happen in the dart-internal pool which does not support LED builds): - 56640: Update certificate and password used for codesigning | https://flutter-review.googlesource.com/c/recipes/+/56640 - 57081: port setup_keychain.sh to dart and upload logs to GCS | https://flutter-review.googlesource.com/c/recipes/+/57081 - 57160: ensure dart sdk from engine checkout is on the path, fix broken usage of flutter/gsutil module, log output to secure log file on failure | https://flutter-review.googlesource.com/c/recipes/+/57160 - 57180: ensure we always log all certificates to secure log file | https://flutter-review.googlesource.com/c/recipes/+/57180 - 57280: Download Apple CA cert and import to keychain. | https://flutter-review.googlesource.com/c/recipes/+/57280 - 57820: Reapply "Use git ref to determine release branch name" | https://flutter-review.googlesource.com/c/recipes/+/57820 Bug: b/333426905 Change-Id: If1e227452179f7330fc3d487952664f3b702e1d4 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/58160 Commit-Queue: Christopher Fujino <fujino@google.com> Reviewed-by: Chris Bracken <cbracken@google.com>
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.
Please follow instructions on Contributing docs to set up your development environment.