What I like most is how well it fits into our CI/CD workflow on GCP. We use it to build container images, push them to Artifact Registry, and then deploy to Cloud Run, all through automated triggers. Once the pipeline is set up, it’s very hands-off and reliable. The integration between Cloud Build, Artifact Registry, and Cloud Run is seamless, which makes the whole flow feel cohesive rather than stitched together. Review collected by and hosted on G2.com.

The YAML configuration can be a bit tricky to get right, especially when setting up more complex pipelines. Also, debugging failed builds isn’t always straightforward; you often have to go through logs step by step to figure out what broke. A bit more clarity in error messages or a more guided setup experience would help. Review collected by and hosted on G2.com.

Google Cloud Build allows us to flexibly develop continuous integration and delivery pipelines for our codebases. It's ease of use and direct integration with source code providers (Github in our case) and close integration with the rest of the GCP ecosystem makes it a vital and easy part of our cloud resource structure. Review collected by and hosted on G2.com.

The Cloud Build YAML file is primarily operated for Cloud Build, meaning less interoperability between other services and greater lock in to the GCP ecosystem. Review collected by and hosted on G2.com.

With Google Cloud Build I don't need to manage servers, it's configuration and maintenance. It is easy to deploy and takes no time at all. Traditionally to deploy my code I had to create a server install dependencies, configure network and what not, but with Google Cloud Build I focus on my code while it handles all the deployment related things. Review collected by and hosted on G2.com.

It does not yet support flutter web(dart). It would be a really great addition to the platform Review collected by and hosted on G2.com.

GCP has modern ecosystem for Devops, including build and deploy Review collected by and hosted on G2.com.

I dont dislike any of as such for google cloud Review collected by and hosted on G2.com.

Google Cloud has very good documentation and easy integration & implementation with good Google customer support. I like to do CI/CD work with GCB and I love using it frequently. It has lots of features that make a developer's life easy. Review collected by and hosted on G2.com.

GCB is a great product but it is very expensive for my many clients. Review collected by and hosted on G2.com.

Flexible build environment - Default or private pools let you choose a build environment that fits your needs.

Broad language and framework support - Build apps in Java, Python, Node, Go, etc. Wide ecosystem support.

Easy to start - Setting up build through UI or YAML config is quick and straightforward. Integrates with GitHub, GitLab, etc.

Automated deployments - Many pre-built deployment integrations with Google Cloud (GKE, Cloud Run, etc.). Can fully automate deployments. Review collected by and hosted on G2.com.

There is no direct support for building Windows containers or executables—only a Linux build environment.

Private pools add management overhead compared to default pools. You have to create and manage the VMs yourself. Review collected by and hosted on G2.com.

It automates frequent tasks & helps to collaborate. It is easy to use with other google tools and i need to pay only for what I use. Review collected by and hosted on G2.com.

If i use it a lot then it starts becoming expensive. Sometimes it gets hang when there is issue with google. Review collected by and hosted on G2.com.

Google Cloud Build has proven to be an invaluable tool in streamlining our continuous integration and delivery (CI/CD) processes. Review collected by and hosted on G2.com.

While the platform is powerful, there is a learning curve, especially for teams new to Google Cloud Build and Understanding and estimating costs can be challenging due to the pricing model's complexity. Clearer cost breakdowns or tools for cost estimation would be beneficial. Review collected by and hosted on G2.com.

The Google Cloud Build provides a seamless and easy deployment feature. The cloud build is triggered whenever a commit is made directly from GitHub. Implementation is very easy and well documented. It can be easily integrated with any VCS. As it is a part of GCP, it comes with a lot of features like pipelines and stages of deployment and also it is fully maintained by the Google support team. It is a very powerful CICD tool that can be frequently used by developers. Review collected by and hosted on G2.com.

The number of VCS repositories can be increased and also the image creation can be a bit more configurable with more options. Review collected by and hosted on G2.com.

Google Cloud Build simplifies the process of continuous integration, allowing our development team to focus on writing code without worrying about manual build and test processes. It seamlessly scales to accommodate our growing development needs. The integration with other Google Cloud services, such as Cloud Source Repositories and Container Registry, creates a cohesive development environment. This has streamlined our workflows and improved collaboration among team members. Setting up automated build triggers based on code changes has significantly improved our development efficiency. The GitHub integration is smooth, allowing us to trigger builds automatically upon pull requests or new commits. Review collected by and hosted on G2.com.

Understanding and estimating costs can be a bit challenging due to the pricing model's complexity. Review collected by and hosted on G2.com.