[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[[["\u003cp\u003eCloud Build supports regional builds in both private and default pools, allowing users to select specific regions for their builds.\u003c/p\u003e\n"],["\u003cp\u003eWhen choosing a region, consider factors like latency, availability, and the location of other integrated Google Cloud services, as multi-location usage can impact latency and pricing.\u003c/p\u003e\n"],["\u003cp\u003eUsers can specify a region when initiating builds via the command line or when creating build triggers, and the selected region for a trigger must match the region of any associated private pool.\u003c/p\u003e\n"],["\u003cp\u003eOnce a private pool is created in a region, it cannot be moved, and Google manages its redundant availability across all zones within that region.\u003c/p\u003e\n"],["\u003cp\u003eSome projects may be restricted to using Cloud Build only in specific regions, such as \u003ccode\u003eus-central1\u003c/code\u003e, \u003ccode\u003eus-west2\u003c/code\u003e, \u003ccode\u003eeurope-west1\u003c/code\u003e, \u003ccode\u003easia-east1\u003c/code\u003e, \u003ccode\u003eaustralia-southeast1\u003c/code\u003e, and \u003ccode\u003esouthamerica-east1\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Cloud Build locations\n\nCloud Build supports regional builds in [private pools](/build/docs/private-pools/private-pools-overview)\nand [default pools](/build/docs/build-push-docker-image).\n\nWhen selecting a region for your builds, your primary considerations should be\nlatency and availability. You can generally select the region closest to your\nCloud Build's users, but you should also consider the location of the\n[other Google Cloud products and services](/about/locations#locations)\nthat your build might integrate with. Using services across multiple locations\ncan affect your app's latency, as well as [pricing](/build/pricing).\n\nCloud Build is available in the following regions:\n\n- `africa-south1`\n- `asia-east1`\n- `asia-east2`\n- `asia-northeast1`\n- `asia-northeast2`\n- `asia-northeast3`\n- `asia-south1`\n- `asia-south2`\n- `asia-southeast1`\n- `asia-southeast2`\n- `australia-southeast1`\n- `australia-southeast2`\n- `europe-central2`\n- `europe-north1`\n- `europe-north2`\n- `europe-southwest1`\n- `europe-west1`\n- `europe-west2`\n- `europe-west3`\n- `europe-west4`\n- `europe-west6`\n- `europe-west8`\n- `europe-west9`\n- `europe-west10`\n- `europe-west12`\n- `me-central1`\n- `me-central2`\n- `me-west1`\n- `northamerica-northeast1`\n- `northamerica-northeast2`\n- `northamerica-south1`\n- `southamerica-east1`\n- `southamerica-west1`\n- `us-central1`\n- `us-east1`\n- `us-east4`\n- `us-east5`\n- `us-south1`\n- `us-west1`\n- `us-west2`\n- `us-west3`\n- `us-west4`\n\nSelect a region\n---------------\n\nTo run regional builds, specify the region when [starting a build\nvia the command line](/build/docs/running-builds/start-build-command-line-api)\nor when [creating a build trigger](/build/docs/automating-builds/create-manage-triggers).\n\nTo select a region for your private pool, specify the region when [creating\nthe private pool](/build/docs/private-pools/create-manage-private-pools#creating_a_new_private_pool).\nOnce you create a private pool within a region, you can't move\nit to another region. When you create a private pool in a specific region, it\nis managed by Google to be redundantly available across\n[all the zones within that region](/docs/geography-and-regions).\n\nIf the\n[build config](/build/docs/configuring-builds/create-basic-configuration) file\nassociated with your trigger specifies a private pool, then the region you\nselect for your trigger must match the region of the private pool.\n\nIf you select `global` as the region for the build trigger, then\nCloud Build uses the region specified in the build config file\nassociated with the trigger to run the build. This can either be the region of\nthe private pool, if you specify a private pool in your build config file, or\nthe global default pool if you don't specify a private pool.\n\nAccess Cloud Build resources using regional endpoints\n-----------------------------------------------------\n\nYou can use regional endpoints to access resources in Cloud Build.\nUsing regional endpoints lets you run your\nworkloads in a manner that complies with\n[data residency](/assured-workloads/docs/data-residency) and data\nsovereignty requirements, where your request traffic is routed directly to the\nregion specified in the endpoint.\n\nRegional endpoints are request endpoints that only allow requests to proceed if\nthe affected resource exists in the location specified by the endpoint. For\nexample, when you use the endpoint\n`https://cloudBuild.me-central2.rep.googleapis.com` in a create builds request,\nthe request only proceeds if the build config file is located in `me-central2`.\n\nUnlike global endpoints, where requests can be processed in a different\nlocation from where the resource resides, regional endpoints guarantee that your\nrequests are processed only within the location specified by the endpoint where\nthe resource resides. Regional endpoints terminate TLS sessions in the location\nspecified by the endpoint for requests received from the Internet, from other\nGoogle Cloud resources (such as Compute Engine virtual machines),from on-premise\nservices using VPN or Interconnect, and from Virtual Private Clouds (VPCs).\n\nRegional endpoints guarantee data residency by ensuring that your\nobject's data at rest and in transit doesn't get moved out of the location\nspecified by the endpoint. This guarantee excludes resource metadata, such as\nobject names and bucket IAM policies. For more information,\nsee\n[Note on Customer Data and Service data](/assured-workloads/docs/data-residency#customer-service-data).\n| **Note:** Regional endpoints support only HTTPS. HTTP isn't supported.\n\nFor information about the steps needed to run a build, see\n[Running builds](/build/docs/running-builds/submit-build-via-cli-api#running_builds).\n\n**Configure the Google Cloud CLI for use with regional endpoints**\n\nTo configure the gcloud CLI for use with regional endpoints, do the\nfollowing:\n\n1. Make sure you're using the Google Cloud CLI 402.0.0 or newer.\n\n2. Set the `api_endpoint_overrides/cloudbuild` property to the regional\n endpoint that you want to use:\n\n ```\n gcloud config set api_endpoint_overrides/cloudbuild https://cloudbuild.LOCATION.rep.googleapis.com/\n ```\n\n Alternatively, you can set the\n `CLOUDSDK_API_ENDPOINT_OVERRIDES_CLOUDBUILD` environment variable to the\n endpoint: \n\n ```\n CLOUDSDK_API_ENDPOINT_OVERRIDES_CLOUDBUILD=https://cloudbuild.LOCATION.rep.googleapis.com/ \n ```\n\nRestricted regions for some projects\n------------------------------------\n\nDepending on usage, certain projects may be restricted to only use Cloud Build\nin the following regions:\n\n- `us-central1`\n- `us-west2`\n- `europe-west1`\n- `asia-east1`\n- `australia-southeast1`\n- `southamerica-east1`"]]
