Agfdhyk

We have a policy in place which restricts resources to EU regions.

When I try to execute a cloud build, gcloud wants to create a bucket (gs://[PROJECT_ID]_cloudbuild) to store staging sources. This step fails, because the default bucket location ('us') is used:

"code": 412,

"message": "'us' violates constraint ‘constraints/gcp.resourceLocations’"

As a workaround I tried to pass an existing bucket located in a valid region (using --gcs-source-staging-dir), but I got the same error.

How can this be solved?

Here the HTTP logs:

$ gcloud --log-http builds submit --gcs-source-staging-dir gs://my-custom-bucket/staging 

--tag gcr.io/xxxxxxxxxx/quickstart-image .

=======================

==== request start ====

uri: https://www.googleapis.com/storage/v1/b?project=xxxxxxxxxx&alt=json

method: POST

== headers start ==

accept: application/json

content-type: application/json

== headers end ==

== body start ==

{"name": "my-custom-bucket"}

== body end ==

==== request end ====

---- response start ----

-- headers start --

server: UploadServer

status: 412

-- headers end --

-- body start --

{

 "error": {

  "errors": [

   {

    "domain": "global",

    "reason": "conditionNotMet",

    "message": "'us' violates constraint ‘constraints/gcp.resourceLocations’",

    "locationType": "header",

    "location": "If-Match"

   }

  ],

  "code": 412,

  "message": "'us' violates constraint ‘constraints/gcp.resourceLocations’"

 }

}



-- body end --

---- response end ----

----------------------

ERROR: (gcloud.builds.submit) HTTPError 412: 'us' violates constraint ‘constraints/gcp.resourceLocations’

Cloud Build will use a default bucket to store logs. You can try to add logsBucket field to the build config file with a specific bucket like in the snippet:

steps:

- name: 'gcr.io/cloud-builders/go'

  args: ['install', '.']

logsBucket: 'gs://mybucket'

You can find detailed information about the build configuration file here