GCP Series: Cloud Build Use Cases on Google Cloud Platform

CloudNerve.com -

Why use Google Cloud Build?

Lets look at some reasons why the GCP Cloud Build tool could work for you.

What is Google Cloud Build?

https://cloud.google.com/build/docs/overview

https://cloud.google.com/build/docs/build-config-file-schema

https://cloud.google.com/build/docs/cloud-builders

https://cloud.google.com/build/docs/iam-roles-permissions

  • Build software quickly across all programming languages, including Java, Go, Node.js, and more

  • Get complete control over defining custom workflows for building, testing, and deploying

  • Deploy across multiple environments such as VMs, serverless, Kubernetes, or Firebase

  • Perform deep security scans as part of your CI/CD pipeline

  • Package source into containers or non-container artifacts such as Maven, Gradle, Go, or Bazel

Key features

Extremely fast builds

Access machines connected via Google’s global network to significantly reduce your build time. Run builds on high-CPU VMs or cache source code, images, or other dependencies to further increase your build speed.

Automate your deployments

Create pipelines as a part of your build steps to automate deployments. Deploy using built-in integrations to Google Kubernetes Engine, App Engine, Cloud Functions, and Firebase. Use Spinnaker with Cloud Build for creating and executing complex pipelines.

Support for multi-cloud

Deploy to multiple clouds as a part of your CI/CD pipeline. Cloud Build comes with builder images which have languages and tools already installed. Likewise containerized tasks of Cloud Build are fully portable across different clouds.

Commit to deploy in minutes

Going from PR to build, test, and deploy can’t be simpler. Set up triggers to automatically build, test, or deploy source code when you push changes to GitHub, Cloud Source Repositories, or a Bitbucket repository.

Unparalleled privacy

Run builds on infrastructure protected by Google Cloud security. Get full control over who can create and view your builds, what source code can be used, and where your build artifacts can be stored.