Jenkins vs Shippable: What are the differences?
Jenkins: An extendable open source continuous integration server. 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; Shippable: Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github & Bitbucket repos. 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.
Jenkins and Shippable can be categorized as "Continuous Integration" tools.
Some of the features offered by Jenkins are:
- Easy installation
- Easy configuration
- Change set support
On the other hand, Shippable provides the following key features:
- 1-Click Setup
- Docker Containers
- Responsive UI
"Hosted internally" is the top reason why over 497 developers like Jenkins, while over 17 developers mention "Free private repositories" as the leading cause for choosing Shippable.
Jenkins is an open source tool with 13.3K GitHub stars and 5.48K GitHub forks. Here's a link to Jenkins's open source repository on GitHub.
Facebook, Netflix, and Instacart are some of the popular companies that use Jenkins, whereas Shippable is used by esa, Reviewable, and Algorithmia. Jenkins has a broader approval, being mentioned in 1774 company stacks & 1526 developers stacks; compared to Shippable, which is listed in 24 company stacks and 4 developer stacks.
What is Jenkins?
What is Shippable?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Shippable?
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.
Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.
- Continuous Deploy
- Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
- Staging and production stages: Build and rollback quicly with Ansistrano playbook
- Sending messages of job results to Chatwork.
Very cheap and good quality integration service. Use docker as the underline infrastructure and is ready to deploy on many places like cloud foundry.
Its a build and reporter tool, continuous building the application
Currently serves as the location that our QA team builds various automated testing jobs.
At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.