| commit | d0ac60f83d64e20a1dbf59a588358b17fd31f61c | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@fuchsia.infra.roller.google.com> | Thu Apr 17 15:33:33 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 17 15:35:29 2025 -0700 |
| tree | 81bfbc776bbfc15183cab39379b0fdd3661b1ec2 | |
| parent | 8d49ea3b4a34038ca524ac4896f62617ca4f4d9f [diff] |
[roll] Roll infra/recipes [coverage] Support triggering on integration.git commits We're removing support from `api.checkout.fuchsia_with_options()` for triggering on commits that aren't in an integration repository. Coverage builders have been triggering on fuchsia.git commit, which will no longer be allowed. Therefore, update the recipe to no longer assume that it's triggered on a fuchsia commit, and instead resolve the fuchsia revision by looking it up via Jiri. We can't switch the builders to trigger on integration.git changes until after this lands because the coverage dashboard only works with fuchsia.git. Original-Bug: 411464876 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1255584 Original-Revision: 8b2df867df05fad8617fa5cc326dd12e0f16b78d GitOrigin-RevId: a7533d304acc928bf4cdbcfa09d7d7b52dbc5a04 Change-Id: I529a689239aa740cf676dbd73f83eefdba90a516
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.