Jenkins vs SourceTree

Overview

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

SourceTree

Stacks10.6K

Followers8.1K

Votes727

Jenkins vs SourceTree: What are the differences?

Introduction

When comparing Jenkins and SourceTree, it is important to understand the key differences between these two tools commonly used in software development.

Integration: Jenkins is a continuous integration and continuous deployment tool that focuses on automating the build, test, and deployment of software. SourceTree, on the other hand, is a GUI tool designed to help manage Git repositories visually and effectively. While Jenkins is primarily focused on automating the development process, SourceTree is more of a visual aid in managing version control.
Functionality: Jenkins is more suited for automation, allowing developers to create pipelines to automate the build, test, and deployment processes. SourceTree, on the other hand, is more of a productivity tool that simplifies Git repository management through its user-friendly interface. While Jenkins streamlines the CI/CD process, SourceTree simplifies version control tasks.
User Base: Jenkins is more commonly used in large-scale enterprise environments where automation of development processes is crucial for efficiency. SourceTree, on the other hand, is popular among individual developers and small to medium-sized teams who prefer a visual representation of their Git repositories. The user base for Jenkins and SourceTree varies based on the specific needs of developers.
Customization: Jenkins is highly customizable, with a wide range of plugins available to extend its functionality and integrate with other tools in the software development lifecycle. SourceTree, on the other hand, offers limited customization options, focusing more on providing a user-friendly interface for managing Git repositories. While Jenkins allows for extensive customization, SourceTree is more static in its features.
Deployment: Jenkins is specifically designed for automating the deployment process, enabling developers to create CI/CD pipelines to streamline the delivery of software. SourceTree, on the other hand, does not offer deployment automation features but focuses on simplifying Git repository management tasks. Jenkins excels in automating deployment processes, while SourceTree is more focused on version control management.
Price: Jenkins is an open-source tool, available for free to use, which makes it accessible to a wide range of developers and organizations. SourceTree, on the other hand, is a proprietary tool developed by Atlassian and comes with licensing fees for commercial use. The difference in pricing between Jenkins and SourceTree may influence the choice of tool based on budget constraints.

In Summary, the key differences between Jenkins and SourceTree lie in their focus on automation vs. visualization, functionality, user base, customization options, deployment features, and pricing models.

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)

Manual

Advice on Jenkins, SourceTree

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

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

Stefan

Jan 19, 2020

Decided

I explored many Git Desktop tools for the Mac and my final decision was to use Fork. What I love about for that it contains three features, I like about a Git Client tool.

It allows

to handle day to day git operations (least important for me as I am cli junkie)
it helps to investigate the history
most important of all, it has a repo manager which many other tools are missing.

198k views198k

Comments

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

529k views529k

Comments

Detailed Comparison

Jenkins	SourceTree
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.	Use the full capability of Git and Mercurial in the SourceTree desktop app. Manage all your repositories, hosted or local, through SourceTree's simple interface.
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	Full-powered DVCS;Create, clone, commit, push, pull, merge, and more are all just a click away.;Review your outgoing and incoming changesets, cherry-pick between branches, patch handling, rebase, stash, shelve, and much more.;Use Git-flow and Hg-flow with ease. Keep your repositories cleaner and your development more efficient with SourceTree's intuitive interface to Git and Hg's 'branchy' development model.
Statistics
GitHub Stars 24.6K	GitHub Stars -
GitHub Forks 9.2K	GitHub Forks -
Stacks 59.2K	Stacks 10.6K
Followers 50.4K	Followers 8.1K
Votes 2.2K	Votes 727
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 Limited abilities with declarative pipelines 7 Lack of support	Pros 205 Visual history and branch view 164 Beautiful UI 134 Easy repository browsing 87 Gitflow support 75 Interactive stage or discard by hunks or lines Cons 12 Crashes often 8 So many bugs 7 Fetching is slow sometimes 5 No dark theme (Windows) 5 Extremely slow
Integrations
No integrations available	GitHub Git Bitbucket Windows macOS Mercurial

What are some alternatives to Jenkins, SourceTree?

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 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.

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 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.

GitKraken

The downright luxurious Git client for Windows, Mac and Linux. Cross-platform, 100% standalone, and free.

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 is a CI/CD developer automation platform designed for Microservices & Container Architecture.

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 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.

Fork

Manage your repositories without leaving the application. Organize the repositores into categories. Fork's Diff Viewer provides a clear view to spot the changes in your source code quickly.

Related Comparisons

Jenkins vs SourceTree: What are the differences?

Introduction

When comparing Jenkins and SourceTree, it is important to understand the key differences between these two tools commonly used in software development.

Integration: Jenkins is a continuous integration and continuous deployment tool that focuses on automating the build, test, and deployment of software. SourceTree, on the other hand, is a GUI tool designed to help manage Git repositories visually and effectively. While Jenkins is primarily focused on automating the development process, SourceTree is more of a visual aid in managing version control.
Functionality: Jenkins is more suited for automation, allowing developers to create pipelines to automate the build, test, and deployment processes. SourceTree, on the other hand, is more of a productivity tool that simplifies Git repository management through its user-friendly interface. While Jenkins streamlines the CI/CD process, SourceTree simplifies version control tasks.
User Base: Jenkins is more commonly used in large-scale enterprise environments where automation of development processes is crucial for efficiency. SourceTree, on the other hand, is popular among individual developers and small to medium-sized teams who prefer a visual representation of their Git repositories. The user base for Jenkins and SourceTree varies based on the specific needs of developers.
Customization: Jenkins is highly customizable, with a wide range of plugins available to extend its functionality and integrate with other tools in the software development lifecycle. SourceTree, on the other hand, offers limited customization options, focusing more on providing a user-friendly interface for managing Git repositories. While Jenkins allows for extensive customization, SourceTree is more static in its features.
Deployment: Jenkins is specifically designed for automating the deployment process, enabling developers to create CI/CD pipelines to streamline the delivery of software. SourceTree, on the other hand, does not offer deployment automation features but focuses on simplifying Git repository management tasks. Jenkins excels in automating deployment processes, while SourceTree is more focused on version control management.
Price: Jenkins is an open-source tool, available for free to use, which makes it accessible to a wide range of developers and organizations. SourceTree, on the other hand, is a proprietary tool developed by Atlassian and comes with licensing fees for commercial use. The difference in pricing between Jenkins and SourceTree may influence the choice of tool based on budget constraints.

Jenkins vs SourceTree

Overview

Jenkins vs SourceTree: What are the differences?