| commit | 24b51bfc50833174764597f51cf90e04e1e3136f | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@fuchsia.infra.roller.google.com> | Thu Jul 11 15:07:42 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 11 08:09:41 2024 -0700 |
| tree | f8982c7f171e568fb5d6fd22f62de69f3b1b3037 | |
| parent | 34ec60975ff821a68949e4e6ccf3fc7143912ca2 [diff] |
[roll] Roll infra/recipes [snap_branch] Don't require source_branch to be a release branch We now set `source_branch = "main"` for the global integration canary snap builder. It's perfectly valid to snap commits from the main branch: we've always done that, but we've used `lkg_builders` to select the commit instead of taking the latest commit. So I see no reason why it would be unsafe to loosen this restriction. Original-Bug: 331826762 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1079832 Original-Revision: 9a82b68a93e376c6d3c98b09b31cd737cf6e10cc GitOrigin-RevId: f224ed124755cc3401cfa1c3e1c1d32a6688ce6a Change-Id: I475f71f170757f1f9401615cd31d3c1b2f02ccd6
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.