Cloud Buildの評判・口コミ 全1件

What do you dislike about the product?

Limited integrations with third-party tools: hile Google Cloud Build integrates smoothly with Google Cloud Source Repositories, it has limited support for repositories hosted on other platforms such as GitLab or Azure DevOps.

What do you like best about the product?

Google Cloud Build effortlessly integrates with other Google Cloud services, such as Google Cloud Source Repositories, Google Container Registry, and Cloud Functions. This tight integration allows for a smooth and streamlined CI/CD workflow within the Google Cloud ecosystem.
we can also trigger builds automatically upon code changes or pull requests from platforms like GitHub and Bitbucket.

What do you dislike about the product?

It has limited features and some limitations when compared to other cloud providers and also it has broken SDKs with high networking prices

And to use this the user/person should have the proper knowledge and the UI feels like experimental

What do you like best about the product?

Mainly I observed it has affordable pricing that offers an enterprise suite to monitor and manage the data and automatically build the source codes (CI) part and deploy the applications

Coming to the orchestration perspective the microservices business applications on the load should be automatically monitored and it should meet the business requirements

What do you dislike about the product?

That there are limited event types that can trigger a cloud build execution, and for that reason, we mainly rely on tags within the repository. The limited support for different OS versions is also a limiting factor as it is mainly Linux based, and we, therefore, cannot use these pipelines for our older Windows-based applications.

What do you like best about the product?

Steps in Cloud Builds jobs can be set up to run in parallel, which makes test and deployment executions noticeably quicker. Then integration with our GitHub repositories works seamlessly, and our CI pipelines execute on every commit to a PR, ensuring that our applications are properly tested before deploys. The support for several containers (cloud builders) makes setting up the build configuration file simple for any application. The documentation the is provided by Google also makes the setup clear and simple. The substitutions created when configuring a pipeline further enable us to make our pipeline configuration files more generic for use across multiple microservices. The ability to manage configurations through IaC services such as Terraform further increases the simplicity and speed at which we can get a Cloud Build trigger setup