[roll] Roll infra/recipes [milestone_roller] Upload CLs even if config generation fails

Config generation is currently failing on this builder due to a race
condition where a CQ-blocking builder was deleted since the new branch's
base commit was created:
https://screenshot.googleplex.com/62p8yUM6CZPUvsF

Currently the only ways to fix this situation are to manually run the
steps that the recipe runs and fix any issues, or to iteratively fix
issues raised by the roller until it's happy.

If we have the roller upload a CL even if it's going to fail CQ, a human
can go in and see why it's failing and amend the CL to make it
submittable, which is a much easier process.

Original-Bug: b/414618041
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1264764
Original-Revision: f010c755cb02c7eab87a215b9393d1057858577c
GitOrigin-RevId: f741d0dee29e1b8b31e3299cf13a43cfb288bebf
Change-Id: I95987e14ea1adca0d163e0deef665d16a35814f3
1 file changed
tree: e9059284e69b80c3d0381accf0bf18edc0dd36c5
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.