Configuration for a WorkerPool to run the builds. Workers are
machines that Cloud Build uses to run your builds. By default, all
workers run in a project owned by Cloud Build. To have full control
over the workers that execute your builds – such as enabling them to
access private resources on your private network – you can request
Cloud Build to run the workers in your own project by creating a
custom workers pool.
The project ID of the GCP project for which the WorkerPool
is created.
Total number of workers to be created across all requested
regions.
List of regions to create the WorkerPool. Regions can’t be
empty. If Cloud Build adds a new GCP region in the future, the
existing WorkerPool will not be enabled in the new region
automatically; you must add the new region to the regions
field to enable the WorkerPool in that region.
Output only. Time at which the request to update the
WorkerPool was received.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-12-13 UTC."],[],[]]
