Jenkins vs. Travis CI vs. Go.CD
|
|
|
||||||
|
|
|
|
||||||
|
No public GitHub repository stats available
|
||||||||
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.
|
What is 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.
|
What is Go.CD?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.
|
||||||
|
|
|
||||||
|
|
|
||||||
Want advice about which of these to choose?Ask the StackShare community! |
||||||||
|
How much does Jenkins cost?
|
How much does Travis CI cost?
|
How much does Go.CD cost?
|
||||||
|
What companies use Jenkins?
2207 companies on StackShare use Jenkins
|
What companies use Travis CI?
878 companies on StackShare use Travis CI
|
What companies use Go.CD?
33 companies on StackShare use Go.CD
|
||||||
|
What tools integrate with Jenkins?
61 tools on StackShare integrate with Jenkins
|
What tools integrate with Travis CI?
45 tools on StackShare integrate with Travis CI
|
No integrations listed yet
|
||||||
What are some alternatives to Jenkins, Travis CI, and Go.CD?
|
||||||||
|
Jenkins is joining the Continuous Delivery Foundation
March 11, 2019
Let's celebrate Java 11 Support on Jenkins
March 10, 2019
Jenkins is accepted to Google Summer Of Code 2019!
March 03, 2019
|
Integrate API tests with Postman, Newman, and Travis CI
August 22, 2017
Running Dusk tests on Travis CI and CircleCI
March 30, 2017
|
|||||||
Related Comparisons
Interest Over Time
Reviews of Jenkins, Travis CI, and Go.CD
-
tschellenbachPerhaps the best CI tool
January 12, 2018 15:14
In the past we used to run Jenkins. The build server always had weird issues and was a pain to maintain. Travis is a great solution for CI. Their Debug build features makes it trivial to figure out why your build broke. The integration with Github is also very slick. One thing they could improve is the documentation on the .travis.yaml format. All in all, great company and very responsive supports. Over here at getstream.io we're a fan. Keep up the good work guys!
Ease of Use Documentation Reliability Support
How developers use Jenkins vs Travis CI vs Go.CD
-
datapile uses Travis CI
Travis CI is our pillar for automated deployment, pull request testing, auto-merging (for non-mission-critical projects), and build testing per commit / release.
It is highly configurable, super cheap, and extremely robust (supports every language and configuration we've thrown at it).
-
Kalibrr uses Jenkins
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.
-
Wirkn Inc. uses Jenkins
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.
-
thanhbn87 uses Jenkins
- 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.
-
cuu508 uses Travis CI
While we usually run tests before commits, Travis goes further and tests with different Python versions and different database backends. It works great, and, best of all, it is free for open source projects.
-
AngeloR uses Jenkins
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.
-
Trusted Shops GmbH uses Jenkins
We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.
-
ruleant uses Travis CI
Travis CI builds and tests every commit. It's also used to deploy Buildtime Trend as a Service to Heroku and the Buildtime Trend Python library to the PyPi repository.
-
scrthq uses Travis CI
Travis CI is critical for Linux and macOS CI tests for the Powershell module. Travis runs the same tests we run in AppVeyor in parallel.
-
skarfacegc uses Travis CI
To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel
