| commit | de7384023477581e83dc9719529fae1e33316a3c | [log] [tgz] |
|---|---|---|
| author | Gwen Mittertreiner <gmtr@fuchsia.infra.roller.google.com> | Thu May 09 19:29:05 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu May 09 12:30:47 2024 -0700 |
| tree | 505da1e2938b420df8b9d5a6cbd44619cd87ad05 | |
| parent | 44e51b34a0b454c6cf4c3948f51901f1e6e7be27 [diff] |
[roll] Roll infra/recipes [checkout] Add Ability to get Internal Revision When uploading to catapult, we'd like to be able to differentiate between public and internal builds. This will allow us to have public facing dashboards based in the public build data. However, internally, we still want to link public commits to the internal commits they derive from. This CL adds the functionality to provide the public commit when available and for public commits, also provide the corresponding internal commit by parsing it from the git commit message. Original-Bug: b/326307398 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1029832 Original-Revision: a3fbfb17d6294f2b4ac22e44cde1a0641d857567 GitOrigin-RevId: b82e7d1382b274d56f51720d57d77a9ac3f1033e Change-Id: I1305519ddff31b3c806fba1ab6b8ee35081a94ec
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 via the IRC channel #fuchsia on Freenode.
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.