Google Cloud Build vs Jenkins

Need advice about which tool to choose?Ask the StackShare community!

Google Cloud Build

493
204
+ 1
4
Jenkins

57.9K
49.4K
+ 1
2.2K
Add tool

Google Cloud Build vs Jenkins: What are the differences?

Google Cloud Build and Jenkins are two popular tools for implementing continuous integration and continuous deployment (CI/CD) pipelines. Let's explore the key differences between Google Cloud Build and Jenkins:

  1. Deployment Platform: Google Cloud Build is a cloud-native CI/CD platform provided by Google Cloud, while Jenkins is an open-source automation server that can be deployed on-premises or in the cloud. Google Cloud Build offers a fully-managed solution that simplifies setup and maintenance, making it particularly suitable for cloud-native projects.

  2. Integration with Google Cloud: As a part of Google Cloud, Cloud Build seamlessly integrates with other Google Cloud services, such as Cloud Storage, Container Registry, and Cloud Functions. This tight integration allows for streamlined workflows and simplified authentication and authorization. Jenkins, on the other hand, can integrate with various tools and platforms but requires additional configuration and plugins for Google Cloud-specific tasks.

  3. Ease of Use: Google Cloud Build focuses on simplicity and ease of use, providing a user-friendly interface and declarative configuration files. With its built-in triggers and automatic build management, it requires less manual setup and configuration compared to Jenkins. Jenkins offers a highly configurable environment but requires more manual effort for setup and maintenance, which can be more suitable for complex or customized CI/CD pipelines.

  4. Scalability and Performance: Google Cloud Build leverages Google Cloud's infrastructure to scale automatically and handle high-demand workloads efficiently. It supports parallel builds and can distribute workloads across multiple machines for improved performance. Jenkins scalability relies on the deployed infrastructure, requiring manual scaling and optimized configuration for handling large-scale projects.

  5. Pricing Model: Google Cloud Build follows a usage-based pricing model, where users pay for the resources utilized, such as build minutes and storage. Pricing tiers are available to accommodate different workload sizes and expectations. In contrast, Jenkins is an open-source tool, and its pricing depends on the infrastructure and cloud provider chosen for deployment, considering compute and storage costs.

  6. Ecosystem and Community Support: Jenkins benefits from a strong open-source community with a vast variety of plugins and integrations available, making it highly extensible and adaptable to different development ecosystems. Google Cloud Build has a smaller but growing ecosystem of extensions and community support, focused on Google Cloud technologies, making it the preferred choice for organizations relying heavily on the Google Cloud Platform.

In summary, Google Cloud Build distinguishes itself as a cloud-native, fully-managed CI/CD platform, tightly integrated with Google Cloud services, offering simplicity, scalability, and optimized pricing, while Jenkins offers great flexibility, extensibility, and community support for diversified environments.

Advice on Google Cloud Build and Jenkins
Needs advice
on
Azure PipelinesAzure Pipelines
and
JenkinsJenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

See more
Replies (1)
Recommends
on
GitHubGitHub

If your source code is on GitHub, also take a look at Github actions. https://github.com/features/actions

See more
Mohammad Hossein Amri
Chief Technology Officer at Planally · | 3 upvotes · 508.9K views
Needs advice
on
GoCDGoCD
and
JenkinsJenkins

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 491.7K views
Recommends
on
Google Cloud BuildGoogle Cloud Build

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Needs advice
on
ConcourseConcourse
and
JenkinsJenkins

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG · | 2 upvotes · 410.8K views
Recommends
on
ConcourseConcourse

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Needs advice
on
JenkinsJenkinsTravis CITravis CI
and
CircleCICircleCI

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

See more
Replies (6)
Dustin Falgout
Senior Developer at Elegant Themes · | 13 upvotes · 564K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit · | 9 upvotes · 875.6K views
Recommends
on
Travis CITravis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more
Recommends
on
Google Cloud BuildGoogle Cloud Build

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
on
Travis CITravis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
on
GitLab CIGitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
on
BuildkiteBuildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
Decisions about Google Cloud Build and Jenkins

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Google Cloud Build
Pros of Jenkins
  • 2
    GCP easy integration
  • 2
    Container based
  • 523
    Hosted internally
  • 469
    Free open source
  • 318
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 211
    Rich set of plugins with good documentation
  • 111
    Has support for build pipelines
  • 68
    Easy setup
  • 66
    It is open-source
  • 53
    Workflow plugin
  • 13
    Configuration as code
  • 12
    Very powerful tool
  • 11
    Many Plugins
  • 10
    Continuous Integration
  • 10
    Great flexibility
  • 9
    Git and Maven integration is better
  • 8
    100% free and open source
  • 7
    Slack Integration (plugin)
  • 7
    Github integration
  • 6
    Self-hosted GitLab Integration (plugin)
  • 6
    Easy customisation
  • 5
    Pipeline API
  • 5
    Docker support
  • 4
    Fast builds
  • 4
    Hosted Externally
  • 4
    Excellent docker integration
  • 4
    Platform idnependency
  • 3
    AWS Integration
  • 3
    JOBDSL
  • 3
    It's Everywhere
  • 3
    Customizable
  • 3
    Can be run as a Docker container
  • 3
    It`w worked
  • 2
    Loose Coupling
  • 2
    NodeJS Support
  • 2
    Build PR Branch Only
  • 2
    Easily extendable with seamless integration
  • 2
    PHP Support
  • 2
    Ruby/Rails Support
  • 2
    Universal controller

Sign up to add or upvote prosMake informed product decisions

Cons of Google Cloud Build
Cons of Jenkins
  • 2
    Vendor lock-in
  • 13
    Workarounds needed for basic requirements
  • 10
    Groovy with cumbersome syntax
  • 8
    Plugins compatibility issues
  • 7
    Lack of support
  • 7
    Limited abilities with declarative pipelines
  • 5
    No YAML syntax
  • 4
    Too tied to plugins versions

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Google Cloud Build?

Cloud Build lets you build software quickly across all languages. Get complete control over defining custom workflows for building, testing, and deploying across multiple environments such as VMs, serverless, Kubernetes, or Firebase.

What is Jenkins?

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Google Cloud Build and Jenkins as a desired skillset
What companies use Google Cloud Build?
What companies use Jenkins?
See which teams inside your own company are using Google Cloud Build or Jenkins.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Google Cloud Build?
What tools integrate with Jenkins?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Mar 24 2021 at 12:57PM

Pinterest

GitJenkinsKafka+7
3
2164
GitJenkinsGroovy+4
4
2702
Dec 4 2019 at 8:01PM

Pinterest

KubernetesJenkinsTensorFlow+4
5
3296
GitGitHubPython+22
17
14236
JavaScriptGitHubPython+42
53
21984
What are some alternatives to Google Cloud Build and Jenkins?
CircleCI
Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
Azure DevOps
Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
GitHub Actions
It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
JavaScript
JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
See all alternatives