Search code examples
githubgoogle-cloud-build

Google Cloud Build mysteriously wrong git hashes

I've been using Google Cloud Build with GitHub triggers without issue for a while now; all of a sudden today, something changed. Somehow the hashes that are showing up in Cloud Build do not correspond to any commits in any of my repositories...

google cloud build wrong git hashes

I've tried searching for documentation, or other folks who've encountered this problem, but found nothing. I uninstalled and reinstalled the GitHub app to no avail.

Has anyone encountered this, and if so, how do you fix it?

EDIT

I found a workaround, looks like builds can be manually run

manual run button

Notice in the build history, the manual run has found a real commit, whereas the build triggered by a push to GitHub is coming up with bogus commits...

manual trigger correct commit, push trigger wrong commit

Solution

  • Check if the issue persists (especially after you trigger a manual run and find back normal existing SHA).

    There was an incident affecting Cloud Tasks scheduler jobs which might have a side-effect on your build status. Considering the incident is resolved, you should not see such an issue again.

    The OP quickshiftin confirms in the comments it was more a GitHub issue than a Google Cloud one:

    • [It] looks like that incident was in us-central1, my servers are in us-west1.
    • Also, I got a response from a GitHub ticket I filed, where they said it appears to relate to changes they made "very recently" and reverted last night.
      As of this morning, the build is working again (nothing changed on my side). > Presumably the issue was from either Google or GitHub.