Cloud Build supports regional builds in private pools and default pools.
When selecting a region for your builds, your primary considerations should be latency and availability. You can generally select the region closest to your Cloud Build's users, but you should also consider the location of the other Google Cloud products and services that your build might integrate with. Using services across multiple locations can affect your app's latency, as well as pricing.
Cloud Build is available in the following regions:
Selecting the region
To run regional builds, specify the region when starting a build via the command line or when creating a build trigger.
To select a region for your private pool, specify the region when creating the private pool. Once you create a private pool within a region, you cannot move it to another region. When you create a private pool in a specific region, it is managed by Google to be redundantly available across all the zones within that region.
If your build config file associated with your trigger specifies a private pool, the region you select for your trigger must match the region of the private pool.
If you select
global as the region for the build trigger, Cloud Build uses the region specified in the build config file associated with the trigger to run the build. This can either be the region of the private pool, if you specify a private pool in your build config file, or the global default pool if you don't specify a private pool.
Restricted regions for some projects
Depending on usage, certain projects may be restricted to only use Cloud Build in the following regions: