Using the default pool
At its initial General Availability (GA) launch in 2017, Cloud Build was designed to provide users with a simple interface and fully managed experience in Google Cloud when building container images and other artifacts such as Go executables or Java archives.
Note
Cloud Build was initially launched under the name Container Builder in 2017, underscoring its simple and focused purpose to provide end users with a way to automate builds.
From its inception, Cloud Build has aimed to ensure the following:
- Users could create builds and triggers for builds by interacting with Google’s API or user interface (UI).
- Users would not need to create, patch, scale, or manage the worker machines that run builds.
- Users would have pre-built integration with logging and monitoring to introspect builds.
Cloud Build first accomplished this experience by providing users with the first mode for workers in Cloud Build: the default pool.