| commit | f41e3b75b4130a12178b7f69211617b4f52caa17 | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@fuchsia.infra.roller.google.com> | Wed Apr 23 08:41:22 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 23 08:42:39 2025 -0700 |
| tree | f168a0845e917e24c2e21382ab6b60e2bd8a6c62 | |
| parent | 97e92b82e9e5640c1ffb98bf959bfb187cac989e [diff] |
[roll] Roll infra/recipes [release] Handle fuchsia.git as an <import> http://tqr/979232 switched fuchsia.git's Jiri manifest entry in integration.git from a <project> to an <import>. Now the <project> entry for fuchsia.git is actually in fuchsia.git, but the pinned revision is still attached to the <import> in integration.git. The release operation recipes previously assumed that every repository's pinned revision was attached to a <project>. Now that that is no longer the case, the release operations need to be able to handle fuchsia.git in its new state. This is very much a quick-and-dirty hack, long-term we should figure out a way to make this more generic and avoid hardcoding fuchsia.git's project name and manifest path. There's also going to be more work required to make these recipes work with projects that are pinned in fuchsia.git. Original-Bug: 385378627 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1258664 Original-Revision: efb8df58b7efc21182cbfe94991f4bae36c3e2ee GitOrigin-RevId: 8bf502f56f19e791586e96d1b549d878498e8c09 Change-Id: Icfe3b21271f99bce0caaddeb7c05e21ab1417114
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.