WorkerPool(mapping=None, *, ignore_unknown_fields=False, **kwargs)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.
Attributes
| Name | Description |
name |
str
User-defined name of the WorkerPool.
|
project_id |
str
The project ID of the GCP project for which the WorkerPool is created.
|
service_account_email |
str
Output only. The service account used to manage the WorkerPool. The service account must have the Compute
Instance Admin (Beta) permission at the project level.
|
worker_count |
int
Total number of workers to be created across all requested regions. |
worker_config |
Configuration to be used for a creating workers in the WorkerPool.
|
regions |
Sequence[
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.
|
create_time |
Output only. Time at which the request to create the WorkerPool was received.
|
update_time |
Output only. Time at which the request to update the WorkerPool was received.
|
delete_time |
Output only. Time at which the request to delete the WorkerPool was received.
|
status |
Output only. WorkerPool Status. |
Classes
Region
Region(value)Supported GCP regions to create the WorkerPool.
Status
Status(value)WorkerPool status