Cloud Build: builds fail trying to fetch git repositories from GitHub

The issue with Cloud Build has been resolved for all affected users as of Sunday, 2021-05-16 09:00 US/Pacific. We thank you for your patience while we worked on resolving the issue.

Summary: Cloud Build: builds fail trying to fetch git repositories from GitHub Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Sunday, 2021-05-16 10:48 US/Pacific. Diagnosis: The problem is limited to GitHub only. The product team is now cooperating with GitHub to troubleshoot the issue on their side. Workaround: Authenticating the repository using GitHub (Legacy) is reported to throw a warning but still complete the builds.

Summary: Cloud Build: builds fail trying to fetch git repos Description: We are experiencing an issue with Cloud Build beginning at Sunday, 2021-05-16 03:00 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2021-05-16 08:45 US/Pacific with current details. Diagnosis: None at this time. Workaround: Authenticating the repository using GitHub (Legacy) is reported to throw a warning but still complete the builds.

Summary: Cloud Build: builds fail trying to fetch git repos Description: We are experiencing an issue with Cloud Build beginning at Sunday, 2021-05-16 03:00 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2021-05-16 06:45 US/Pacific with current details. Diagnosis: None at this time. Workaround: Authenticating the repository using GitHub (Legacy) is reported to throw a warning but still complete the builds.

Summary: Cloud Build: builds fail trying to fetch git repos Description: We are experiencing an issue with Cloud Build beginning at Sunday, 2021-05-16 03:00 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2021-05-16 05:45 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: None at this time. Workaround: Authenticating the repository using GitHub (Legacy) is reported to throw a warning but still complete the builds.