GitHub vs. Jenkins

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
GitHub
Score 9.0 out of 10
N/A
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$40
per year per user
Jenkins
Score 8.3 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.N/A
Pricing
GitHubJenkins
Editions & Modules
Team
$40
per year per user
Enterprise
$210
per year per user
No answers on this topic
Offerings
Pricing Offerings
GitHubJenkins
Free Trial
YesNo
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
GitHubJenkins
Considered Both Products
GitHub
Chose GitHub
GitHub comes handy in terms of usage and capabilities, it is easy to use and quite a user friendly tools when it comes to user experience, with limited UI/UX and it has vast exposure when it comes to third party integration and being quite mature and yet evolving and popular …
Chose GitHub
Over my career I've used a variety of other platforms but always find myself coming back to GitHub which has always had the most forward thinking features, evolving faster than other platforms, staying on the cutting edge of AI and other tools as they are released. AI …
Chose GitHub
GitLab has strong code review and project management capabilities, but it has a smaller community. Better for cross-functional collaboration but less intuitive for nontechnical users.
Chose GitHub
GitHub has best in class UI, massive open source base. GitHub actions are very flexible and pricing is very competitive.
Chose GitHub
Bitbucket in most cases is very similar. Though the UI and collaboration tools are much easier to use overall on GitHub.
Chose GitHub
GitHub compared to Gitlab and Bitbucket seems to have an easier and nice to use interface. This is mainly due to the fact that GitHub is the No1 choice for most of the Open Source projects. Developers out there are already famaliar to it's UX/UI and use it every day.

Another …
Chose GitHub
GitHub is primarily targeted at developers and open-source communities, while Bitbucket is geared more towards small- to medium-sized businesses. GitHub has a free plan for open-source projects, while Bitbucket charges a fee for private repositories. For organizations with …
Chose GitHub
Github has much better code view/search/edit power versus bitbucket, and is the industry standard for professional software developers.
Chose GitHub
GitHub is the best platform to manage your source code. You can manage your CI/CD with different cloud service provider platforms and different languages. You can also create GHE for a number of organizations and repositories. Learning GitHub is easy and simple and supports …
Chose GitHub
GitHub stacks up against all of its competitors due to its ease of use and great UI that tops the all. I selected GitHub considering its popularity greater developer community. GitHub also provides Student Developer Pack that we can use to enhance our knowledge and get up to …
Chose GitHub
While SVN comes with basic functionalities, TFS is a superior tool and often unused to its potential in most cases. GitHub brings that equilibrium. It perfectly works like a versioning tool and can also be used to create CICD deployment pipelines.
Chose GitHub
GitHub is distributed model while perforce is more centralised .i.e. Developers can easily download full change history.
Git is better in terms of performance as it provides faster result.
Also Git is open source and available free of cost. Git is also storage effective with …
Chose GitHub
One biggest reason is that GitHub is popular and used by many so it is easy to get contributions this also means that most people are already familiar with using GitHub. Gitlab does offer more features and has more rich pipelines with the free repository as well but GitHub is …
Chose GitHub
GitHub is awesome at it's own place. I'm using it from last 3 years and not used so Gitlab or Bitbucket so much. They are also having almost same features but i think one of then is free for multiple branches.
Chose GitHub
GitHub gives support for open-source applications. I think it has an easier and more reliable interface compared to other products on the market. You are able to expose your work via GitHub so that it can be used as a proof of your work to your current employer or future …
Chose GitHub
It was the broader set of features and how easy it is to browse the history that made us change to GitHub, and time has proven us right.
Chose GitHub
GitHub is the de-facto solution for version control and code storage. Our team prefers it over other options like BitBucket for its feature-completeness.
Chose GitHub
GitHub is at least as good as BitBucket, if not a little more refined. GitHub is hands-down better than TFS. If you are using TFS, you really need to move to a modern source control system. The newer Azure DevOps Server has a decent Git offering, but the UX is incredibly …
Chose GitHub
BitBucket is a very similar tool, but you can have multiple private repositories and it's easy to integrate it with JIRA.
Chose GitHub
In the past, we used Beanstalk and were happy with it. Going forward, GitHub makes it easier for us to work with open-source projects and with new temporary developers who might not be familiar with Beanstalk.
Chose GitHub
GitLab is my personal preference for source control, primarily because of the fact that it is open-source, and that it has great CI tools integrated directly into the service. However, GitHub is probably the leader with respect to enterprise offerings. GitHub has many more …
Jenkins
Chose Jenkins
Jenkins is highly customizable, making it ideal for complex pipelines that require scripting, conditional logic, and integration with a variety of tools.Jenkins offers thousands of plugins, giving it unmatched versatility.
Chose Jenkins
Jenkins is highly customizable and flexible, supporting a wide range of plugins and integrations. Jenkins works with any version control system (Git, Subversion, etc.). Jenkins has a more mature ecosystem, and it may be better for large-scale, complex environments, especially …
Chose Jenkins
One of the most important factors for selecting Jenkins would be the cost. Since Jenkins is opensource, there is a good amount saved from licensing and software procurement costs. Apart from cost, Jenkins is easy to understand and there is wide range of documentation and …
Chose Jenkins
Bitbucket building was very slow, in order to improve that you have to upgrade to spend double or more minutes per build minute. The GUI was also very slow in updating on the progress of the builds, making things rather confusing. Gitlab worked a bit better in my opinion, but …
Chose Jenkins
Jenkins is very easy to use, open source tool. Its better for simple build and deployments.
Chose Jenkins
GitLab CI and Github Actions are other powerful options in the market also with a rising popularity and high interoperability with their respective platform.
But Jenkins is still a good option for complex pipelines that require scripting and logic. Also, Jenkins uses as runtime …
Chose Jenkins
I have used Spinnaker as a CD tool. Though it's a very powerful CD tool we still needed Jenkins for CI, so to save some hassle for us we opt Jenkins solely.
Chose Jenkins
Didn't really check other tools in detail since Jenkins served all our requirements and has been hugely popular.
Chose Jenkins
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used …
Chose Jenkins
Honestly, we use Jenkins for pretty much everything exclusively, so it's hard to compare.
Chose Jenkins
It's mostly stable and well-known within the DevOps community.
Chose Jenkins
We have not evaluated other similar products.
Chose Jenkins
Both Jenkins and TeamCity do a good job of automating CI/CD. Jenkins runs much leaner than TeamCity - it only needs about a Gig of free memory, whereas TeamCity needs a fat 4 Gig free. Many tasks in Jenkins yml config can be very cumbersome, especially running local and …
Chose Jenkins
Jenkins is the only solution that we've tried that just automatically generates builds.
Chose Jenkins
Jenkins is easy to set up and supports a wide range of plugins. So any type of deployment is very easy. We can easily deploy Node, Angular, React, Java, Python, etc. Projects. We can also provide different credentials to different employees. So easy to track what is done by …
Chose Jenkins
Team services, while very similar, did not really have that much more added features for the much higher price tag. The team has moved over to the subscription-based Visual Studio so we may be reevaluating this solution as now it is part of our subscription and no longer an …
Chose Jenkins
I don't have any experience with alternatives to Jenkins.
Chose Jenkins
Originally Jenkins was selected because it was the best around, but it has since been outclassed by more specific services or cloud-based services and tools that will do all of the heavy lifting for you. Jenkins still has a use case - but it's hard to argue the additional …
Chose Jenkins
The big difference between Jenkins and other alternative tools is that Jenkins is open source and it’s free. Jenkins is very much about simple functionality. It’s a general CI tool that offers basic automation. It’s the most common CI tool on the market with a large community …
Chose Jenkins
We went with drone.io ultimately for its first class support for container based workloads.
Chose Jenkins
We considered using Gitlab, but after some comparing, we found Jenkins was better in every way!
Chose Jenkins
Chef and Puppet Pipelines (formerly Distelli)
Features
GitHubJenkins
Version Control Software Features
Comparison of Version Control Software Features features of Product A and Product B
GitHub
7.9
Ratings
4% below category average
Jenkins
-
Ratings
Branching and Merging9.80 Ratings00 Ratings
Version History8.00 Ratings00 Ratings
Version Control Collaboration Tools7.10 Ratings00 Ratings
Pull Requests9.60 Ratings00 Ratings
Code Review Tools7.80 Ratings00 Ratings
Project Access Control8.10 Ratings00 Ratings
Automated Testing Integration7.40 Ratings00 Ratings
Issue Tracking Integration4.10 Ratings00 Ratings
Branch Protection9.40 Ratings00 Ratings
Best Alternatives
GitHubJenkins
Small Businesses
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.7 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
GitLab
GitLab
Score 8.7 out of 10
Enterprises
Perforce P4
Perforce P4
Score 7.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
GitHubJenkins
Likelihood to Recommend
8.9
(0 ratings)
7.5
(0 ratings)
Likelihood to Renew
10.0
(0 ratings)
-
(0 ratings)
Usability
10.0
(0 ratings)
7.9
(0 ratings)
Performance
-
(0 ratings)
8.9
(0 ratings)
Support Rating
8.8
(0 ratings)
6.6
(0 ratings)
Implementation Rating
-
(0 ratings)
6.0
(0 ratings)
User Testimonials
GitHubJenkins
Likelihood to Recommend
I’ve worked with Github my entire career and view it as an essential part. As a Product manager it allows me to keep track of my features, epics, issues and QA. It is easy to set up and integrate with tools such as intercom or notion.
Read full review
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Read full review
Pros
  • Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
  • Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
  • Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
Read full review
  • Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
  • Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
  • Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
Read full review
Cons
  • Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
  • Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
  • Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
  • While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
Read full review
  • Jenkins can be vulnerable to security issues due to its open-source nature and the availability of many third-party plugins. There have been instances where malicious plugins have been discovered, and these can pose a significant risk to organisations.
  • Jenkins can require a significant amount of maintenance, particularly when dealing with plugin updates and compatibility issues. Maintaining a stable and up-to-date Jenkins instance can be a challenge for organisations with limited resources.
  • Jenkins' reporting capabilities are limited, and it can be challenging to extract meaningful insights from the data that Jenkins provides.
Read full review
Likelihood to Renew
GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.
Read full review
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
Read full review
Usability
GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.
Read full review
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
Read full review
Performance
No answers on this topic
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
Read full review
Support Rating
It's a testament to how easy it is to use GitHub and how many others use it that you can pretty much find the answer to any problem you have by searching online. Consequently, I've never needed to use their support. It's an incredibly easy tool to set up initially, so it won't require much onboarding expertise to get started.
Read full review
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
Read full review
Implementation Rating
No answers on this topic
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
Read full review
Alternatives Considered
GitHub comes handy in terms of usage and capabilities, it is easy to use and quite a user friendly tools when it comes to user experience, with limited UI/UX and it has vast exposure when it comes to third party integration and being quite mature and yet evolving and popular tool many other platform provide easy integration with the platform and make first choice for many tools architects.
Read full review
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
Read full review
Return on Investment
  • GitHub has made branching much easier for our dev team. Easy branching makes it easier for us to gain all the benefits of source control while giving us the flexibility to decide what features/branches we want to go in any particular release.
  • Integration with third-party tools like Azure DevOps has allowed us to streamline workflows and gain the benefits of automated testing whenever a commit is made.
  • GitHub has also raised visibility with its integration with our Sprint boards. We can easily jump to a commit from a work item.
Read full review
  • We run about 30 test projects through Jenkins every day, multiple times a day; this allows us to focus on new tests rather than manually running all these tests.
  • We rely heavily on reporting capabilities and email notifications; we have some jobs that send emails every time they run so we know if there is an issue with any of our services.
Read full review
ScreenShots