| commit | b46ae8fddc4689c5248146e1ba55dac6874581b1 | [log] [tgz] |
|---|---|---|
| author | Anthony Fandrianto <atyfto@fuchsia.infra.roller.google.com> | Wed Apr 21 22:55:10 2021 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 21 15:56:04 2021 -0700 |
| tree | 4b35efeb4f7d9072e89d398941d761fcbb4f1962 | |
| parent | 995e8d7d6c4bd83006bd0a68f56cfc0f38b4e770 [diff] |
[roll] Roll infra/recipes [snap_branch] Add option to no-op on mismatched milestones When a branch is created, say F3, we have a MILESTONE roller to detect the new branch and bump the value from 3 to 4 at tip-of-tree. At the same time, an automated snapper may continue to find an LKG which is behind the MILESTONE roll, and create a 3.B.C.D version. This is not desirable because we do not want to create any more 3.B.C.D versions off tip-of-tree LKGs after branching F3. The option `must_match_milestone` checks that the resolved release version's milestone matches the milestone at HEAD, or otherwise no-ops with SUCCESS status. Essentially, when this option is on, automated tip-of-tree snappers will wait to snap until the CI LKG has caught up the new MILESTONE number. Original-Bug: 75095 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/519420 Original-Revision: 9b87f93007900e945e0c8d5cd4a8778c432d3d32 GitOrigin-RevId: 69dc25e82b46ecb5bdc58ff4dc1cc0105bcd4e39 Change-Id: I3d29fdd0588c8d4087cfde5d61efdee17548149d
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.