Obsolete
Status Update
Comments
ma...@syntio.net <ma...@syntio.net> #2
FYI
ma...@syntio.net <ma...@syntio.net> #3
Update: The issue is finally solved!!
I still don't understand what caused the internal error, but the solution was to disable and re-enable the Cloud Build API. Once I did that, everything started working fine. Very unusual, in my opinion.
At one point, I decided to try replicating everything in a different GCP project. The same configuration that was giving me the internal error worked without problems there, so I concluded that something was likely off with the original project I was working on. That's what ultimately led to the solution mentioned above.
Description
Problem you have encountered
I encountered an internal error when running a Cloud Build trigger in my Google Cloud project. The error occurs consistently upon triggering the build and results in the build process failing immediately without executing the intended steps.
Error Details
13
(INTERNAL)<my-project-id>@cloudbuild.gserviceaccount.com
projects/<my-project-name>/triggers/<trigger-hash-id>
europe-west6
Snippet from the log message
Here’s a snippet from the log message:
What you expected to happen
The Cloud Build trigger should initiate the build process and execute the steps defined in the cloudbuild.yaml file without errors. The build logs should be generated as per the configuration, and the build should complete successfully.
Additionally, I’m unsure why the default Cloud Build service account (<my-project-id>@cloudbuild.gserviceaccount.com) is always used, instead of the custom service account I specified when creating the trigger. I set this custom service account as my preferred service account in the settings too, yet it’s not being used.
Steps to reproduce
cloudbuild.yaml
configuration file with basic steps (e.g., echoing "Hello, World!").CLOUD_LOGGING_ONLY
in the configuration.Here is one of the
cloudbuild.yaml
configurations I tried to use:Workarounds and Attempts
roles/logging.logWriter
).Unhelpful Documentation
The error doesn’t seem to be covered in the standard troubleshooting guides for Cloud Build.
Request for Assistance
I would appreciate guidance on whether this is a known issue with Cloud Build or specific to my configuration. Any potential workarounds or additional troubleshooting steps would also be helpful.