Google revealed a new stand-alone tool called "Google Cloud Container Builder," used for developing container images, regardless of deployment environment. The new tool has reached general availability status after a year running Google App Engine's gcloud app deploy operation.
"Whether you're a large enterprise or a small startup just starting out with containers, you need a fast, reliable, and consistent way to package your software into containers as part of an automated workflow," explained Google.
"Container Builder enables you to build your Docker containers on GCP. This helps empower a tighter release process for teams, more reliable build environment across workspaces and frees you from having to manage your own scalable infrastructure for running builds."
How does it work?
The Container Builder allows users to build Docker containers on the Google Cloud Platform (GCP). Users create Docker container images from application source code located in the Google Cloud Storage. Container images are automatically stored in the Google Container Registry. And the build artifacts will work wherever you can run applications from Docker containers, as well as other Google services, including: the Container Engine, Compute Engine or the App Engine flexible environment.
Specs of Cloud Container Builder include:
REST API and Cloud SDK
Container Builder provides a REST API for
programmatically creating and managing builds as well as a gcloud
command line interface for working with builds from the CLI. Google provides online
documentation that includes examples using the Cloud SDK and curl that will
help enable the user to integrate Container Builder into their workflows.
UI and Automated Build Triggers
Builder enables two new UIs in the Google Cloud Console under Container
Registry, build history and build triggers. Build triggers lets you
set up automated CI/CD workflows that start new builds on source code
changes. Triggers work with Cloud Source Repository, Github, and
Bitbucket on pushes to your repository based on branch or tag. Build history helps users track their history by showing details for each build, including logs.
Google has additionally provided a series of quick-start tutorials to
facilitate initial builds, including the traditional Hello World
example, hosted at GitHub.
It is also important to note, Google Cloud Container Builder
is not only about Docker.
Google describes it as a "composable ecosystem," and they've provided open
source builders for common languages and tasks, including git,
go, npm and the gcloud command line interface.
Google also stated that many images on DockerHub like Maven, Gradle and Bazel will work out of the box. And by composing custom build steps, a user can run unit tests with those builds, reduce the size of the final image by re-baking the built image onto a leaner base image, and removing build and test tooling and much more.
Container Builder includes 120 free build minutes per day per billing account, enabling most users to move their builds to the cloud at no cost and
with none of the overheads of managing their own servers. Additional
build-minutes beyond 120 minutes can be had at a cost of $.0034 per minute. The company has also provided more detailed pricing information