Service Health

We apologize for the inconvenience this service disruption/outage may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. If you have experienced impact outside of what is listed below, please reach out to Google Support by opening a case using https://cloud.google.com/support.

(All Times US/Pacific)

Incident Start: 02 February 2022 12:00

Incident End: 09 February 2022 05:48

Duration: 6 days, 17 hours, 48 minutes

Affected Services and Features:

Cloud Build

Regions/Zones: Global

Description:

Creating Cloud Build GitHub triggers in the Cloud Console failed when the URL of the page ended with a project ID as the last argument (e.g. https://console.cloud.google.com/cloud-build/triggers/add?project=project-id-1234) Creation of triggers via gcloud was not impacted. From preliminary analysis, the root cause of the issue was that the Cloud Console began sending resource names in a format Cloud Build could not parse.

Customer Impact:

Customers attempting to create GitHub triggers when using a Cloud Console URL that ended in their project ID would have experienced pages that displayed “Failed to load” errors.

The issue with Cloud Build has been resolved for all affected projects as of Wednesday, 2022-02-09 05:48 US/Pacific.

We thank you for your patience while we worked on resolving the issue.

Summary: Global: Cloud build unable to create github triggers

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 Wednesday, 2022-02-09 07:00 US/Pacific.

Diagnosis: Customers attempting to create github triggers using a Cloud Console URL that ends in their project id (example: https://console.cloud.google.com/cloud-build/triggers/add?project=$project-id) will see a "Failed to load" error with following message: "There was an error while loading /cloud-build/triggers?project= Please try again"

Workaround: Modify the URL in the browser to end with the project number instead of project id

e.g. https://console.cloud.google.com/cloud-build/triggers/add?project=$project-num

Summary: Global: Cloud build unable to create github triggers

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 Tuesday, 2022-02-08 15:00 US/Pacific.

Diagnosis: Customers attempting to create github triggers using a Cloud Console URL that ends in their project id (example: https://console.cloud.google.com/cloud-build/triggers/add?project=$project-id) will see a "Failed to load" error with following message: "There was an error while loading /cloud-build/triggers?project= Please try again"

Workaround: Modify the URL in the browser to end with the project number instead of project id

e.g. https://console.cloud.google.com/cloud-build/triggers/add?project=$project-num

Summary: Global: Cloud build unable to create github triggers

Description: We are experiencing an issue with Cloud Build beginning at Wednesday, 2022-02-02 12:00 US/Pacific.

Our engineering team continues to investigate the issue.

We will provide an update by Tuesday, 2022-02-08 13:30 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: Customers will see a "Failed to load" error with following message: "There was an error while loading /cloud-build/triggers?project= Please try again"

Workaround: Modify the URL in the browser to end with the project number

e.g. https://console.cloud.google.com/cloud-build/triggers/add?project=$project-id ---> https://console.cloud.google.com/cloud-build/triggers/add?project=$project-num

Summary: Global: Cloud build unable to create github triggers

Description: We are experiencing an issue with Cloud Build beginning at Wednesday, 2022-02-02 12:00 US/Pacific.

Our engineering team continues to investigate the issue.

We will provide an update by Tuesday, 2022-02-08 12:00 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: Customers will see a "Failed to load" error with following message: "There was an error while loading /cloud-build/triggers?project= Please try again"

Workaround: Modify the URL in the browser to end with the project number

e.g. https://console.cloud.google.com/cloud-build/triggers/add?project=$project-id ---> https://console.cloud.google.com/cloud-build/triggers/add?project=$project-num