Failed to trigger build: set either CLOUD_LOGGING_ONLY / NONE logging options

I'm usually very AWS but sometimes we have to deal with unfamiliar clouds. Failed to trigger build: if 'build.service_account' is specified, the build must either (a) specify 'build.logs_bucket', (b) use the REGIONAL_USER_OWNED_BUCKET build.options.default_logs_bucket_behavior option, or (c) use either CLOUD_LOGGING_ONLY / NONE logging options: invalid argument Are you hitting this error straight from creating a GCP Cloud Build trigger with absolutely no way to enable CLOUD_LOGGING_ONLY because it's not actually in the UI anywhere for you to edit? Well I just spent the last two hours trying to figure this out too. Hopefully I can help you. Firstly install the gcloud cli tool - Apologies but I could not find a way to fix this in the browser. Next, dump your configuration to a yaml file $ gcloud beta builds triggers export your-trigger-name --destination=trigger-config.yaml When I look at my trigger-config.yaml, I have an empty options field: build: images: - gcr.io/your-repo:$COMMIT_SHA options: {} steps: - args: - build ... What we need to is add logging: CLOUD_LOGGING_ONLY to this and remove the curly braces. It should look like: build: images: - gcr.io/your-repo:$COMMIT_SHA options: logging: CLOUD_LOGGING_ONLY steps: - args: - build ... Then import the new settings back to the trigger cloud beta builds triggers import --source=trigger-config.yaml Now you can manually trigger your... trigger and it should succeed.

Apr 14, 2025 - 07:07

Failed to trigger build: set either CLOUD_LOGGING_ONLY / NONE logging options

I'm usually very AWS but sometimes we have to deal with unfamiliar clouds.

Failed to trigger build: if 'build.service_account' is specified, the build must either (a) specify 'build.logs_bucket', (b) use the REGIONAL_USER_OWNED_BUCKET build.options.default_logs_bucket_behavior option, or (c) use either CLOUD_LOGGING_ONLY / NONE logging options: invalid argument

Are you hitting this error straight from creating a GCP Cloud Build trigger with absolutely no way to enable CLOUD_LOGGING_ONLY because it's not actually in the UI anywhere for you to edit?

Well I just spent the last two hours trying to figure this out too. Hopefully I can help you.

Firstly install the gcloud cli tool - Apologies but I could not find a way to fix this in the browser.

Next, dump your configuration to a yaml file

$ gcloud beta builds triggers export your-trigger-name --destination=trigger-config.yaml

When I look at my trigger-config.yaml, I have an empty options field:

build:
  images:
  - gcr.io/your-repo:$COMMIT_SHA
  options: {}
  steps:
  - args:
    - build
 ...

What we need to is add logging: CLOUD_LOGGING_ONLY to this and remove the curly braces.

It should look like:

build:
  images:
  - gcr.io/your-repo:$COMMIT_SHA
  options:
    logging: CLOUD_LOGGING_ONLY
  steps:
  - args:
    - build
 ...

Then import the new settings back to the trigger

cloud beta builds triggers import --source=trigger-config.yaml

Now you can manually trigger your... trigger and it should succeed.