Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Attachment actions
Description
But I constantly experience flacky "couln't read commit" sitation, where Cloud Build can not read the linked repo. The situtation is flacky -- at some point it stops reproducing without any actions from my side. But eventually I experience this every day. Homegrown component works fine in the very same time.
I guess GCP needs to:
1. Monitor this situation. Especially to track the flacky cases, where the same BitBucket Cloud repo goes online after being inaccessible. The problem persists for more than 6 months with no visible progress from GCP.
2. Add some retries or exception handling in the BitBucket Cloud integration component for repositieries v2 in Cloud Build.