Cloud build not executed by cloud build service account

[thgsponer]

I've set up a new GCP project and configured googleCloudRunner. It is my third project I did following googleCloudRunners setup instructions.

Now, I observe a strange behaviour:

• In the first project, the cloud build was executed by xxxxx@cloudbuild.gserviceaccount.com.
• In the second project, the cloud build was executed by xxxxx@cloudbuild.gserviceaccount.com in 2024, but in March 2025 it was executed by yyyyy@my-project.iam.gserviceaccount.com. This one I have set up for a newly deployed VM.
• Last week I've setup the new project and the cloud build is executed by xxxx-compute@developer.gserviceaccount.com

In my new project, I want read serctets from the secret manager. So, I noticed this behaviour because the compute service account does not have persmissions to read the secrets from the secret manager and therefore the build failed. I gave these permissions to the service account created along the cr_setup - process, since I thought this was the trigger/executor of the build.

Apparently I do not understand what is going on.

Is there a way to specify which service account should be used to execute the cloud build?

[MarkEdmondson1234]

Yes you can specify a unique service account for cloud build, are you looking to do that in GCP or this package?