StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Jenkins vs VMware vSphere

Jenkins vs VMware vSphere

OverviewDecisionsComparisonAlternatives

Overview

Jenkins
Jenkins
Stacks59.2K
Followers50.4K
Votes2.2K
GitHub Stars24.6K
Forks9.2K
VMware vSphere
VMware vSphere
Stacks608
Followers550
Votes30

Jenkins vs VMware vSphere: What are the differences?

Key Differences between Jenkins and VMware vSphere

Jenkins and VMware vSphere are two widely used tools in the DevOps and virtualization space. While both tools serve different purposes, there are several key differences between them.

  1. Purpose: Jenkins is an open-source automation server that is primarily used for continuous integration and continuous delivery (CI/CD) pipelines. It allows developers to automate the build, test, and deployment of software applications. On the other hand, VMware vSphere is a virtualization platform that enables the creation and management of virtual machines and virtual infrastructure. It is commonly used for server virtualization and cloud computing.

  2. Target Audience: Jenkins caters to software development teams and organizations that aim to establish efficient CI/CD workflows. It provides numerous plugins and integrations that developers can utilize to automate their software processes. In contrast, VMware vSphere targets IT administrators and organizations that require virtualization capabilities to consolidate their server infrastructure or build private clouds.

  3. Functionality: Jenkins is primarily focused on automating software development processes. It provides features such as version control integration, unit testing, code analysis, and deployment automation. VMware vSphere, on the other hand, offers a wide range of virtualization functionalities like memory management, resource pooling, virtual networking, and high availability.

  4. Licensing: Jenkins is an open-source tool and is available for free under the MIT License. It has a large community of contributors who continuously enhance its features and provide support. On the contrary, VMware vSphere is a proprietary tool and requires the purchase of licenses based on the number of hosts or processors being used. It offers different editions with varying levels of advanced features and support.

  5. Scalability and Performance: Jenkins is designed to be highly scalable and can handle large-scale software development projects with ease. It supports distributed builds and can be configured to run on multiple machines for parallel processing. VMware vSphere is built for scalability as well, enabling the creation and management of multiple virtual machines on a single physical server or across a cluster of servers. It provides features like distributed resource scheduling and load balancing to optimize performance.

  6. Community and Support: Jenkins has a vast and vibrant community of users and contributors who actively share knowledge, develop plugins, and provide support through forums, mailing lists, and documentation. As an open-source tool, the community plays a crucial role in its growth and evolution. VMware vSphere also has a significant user base and offers support in the form of documentation, knowledge base articles, and a dedicated support team. However, its community involvement is generally not as prominent as Jenkins.

In Summary, Jenkins is an open-source automation server focused on CI/CD processes, while VMware vSphere is a virtualization platform for managing virtual machines and infrastructure. They differ in purpose, target audience, functionality, licensing, scalability, and community support.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Jenkins, VMware vSphere

Balaramesh
Balaramesh

Apr 20, 2020

Needs adviceonAzure PipelinesAzure Pipelines.NET.NETJenkinsJenkins

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.

663k views663k
Comments
StackShare
StackShare

Apr 17, 2019

Needs advice

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?"

530k views530k
Comments
Tatiana
Tatiana

Nov 16, 2019

Decided

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.

734k views734k
Comments

Detailed Comparison

Jenkins
Jenkins
VMware vSphere
VMware vSphere

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.

vSphere is the world’s leading server virtualization platform. Run fewer servers and reduce capital and operating costs using VMware vSphere to build a cloud computing infrastructure.

Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support
Powerful Server Virtualization;Network Services;Efficient Storage;Consistent Automation;High Availability;Robust Security
Statistics
GitHub Stars
24.6K
GitHub Stars
-
GitHub Forks
9.2K
GitHub Forks
-
Stacks
59.2K
Stacks
608
Followers
50.4K
Followers
550
Votes
2.2K
Votes
30
Pros & Cons
Pros
  • 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
Cons
  • 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
Pros
  • 8
    Strong host isolation
  • 6
    Industry leader
  • 5
    Great VM management (HA,FT,...)
  • 4
    Easy to use
  • 2
    Great Networking
Cons
  • 9
    Price

What are some alternatives to Jenkins, VMware vSphere?

Travis CI

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

VirtualBox

VirtualBox

VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2.

CircleCI

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.

TeamCity

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana