Hacker News, Reddit, Stack Overflow Stats
No public GitHub repository stats available
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 CircleCI?
CircleCI’s continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. CircleCI offers a modern software development platform that lets teams ramp
Pros about this tool
Cons about this tool
1459 Companies Using Jenkins
551 Companies Using Travis CI
698 Companies Using CircleCI
Travis CI Integrations
What are some alternatives to Jenkins, Travis CI, and CircleCI?
Perhaps 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!
Easy to setup, great flexibility, awesome support
January 21, 2018 21:02
After trying several CI systems, we stuck with CircleCI because of the inference engine in CircleCI 1.0 made setup a breeze. We were up and running quickly. Builds are reliable, nicely integrated into GitHub, and anytime we've had a question, the support team was there to help. The 2.0 system provides Docker support and far more customization and is still fairly easy to set up with helpful documentation.
Easy to use and super quick
February 15, 2018 11:36
I use CircleCI as part of a cross platform mobile app to build and test the app as well as deploying .apk files to an s3 bucket.
Alongside CircleCI this repo also has a TravisCI setup for iOS. The CircleCI build has always been quicker and since moving from CircleCI v1 to CircleCI v2 it blows the TravisCI build out of the water. I'm really impressed with the performance gains from moving to v2. I'm pretty sure I could achieve similar results in Travis as well, but it was really easy to setup the Android CI build in Circle making use of Docker.
The Best CI
January 30, 2018 17:21
The best CI ever. The easy way you can configure to run your project is amazing!
The ultimate CI tool that you need.
February 07, 2018 10:12
Circle CI is stable, fast, easy to start and has a huge amount of things which you can do with it.
Good availability, stays current, great ease of use
February 07, 2018 11:04
CircleCI has become our CI of choice. The UI is really good and it has all the integrations we need. The 2.0 upgrade was not yet possible for one of our projects due to outdated gems, however, I have been able to get it working for a different one.
CircleCI is an integral part of our CD pipeline
February 28, 2018 12:23
We use it to test every commit we push to github and deploy everything we merge into master for every project.
Easy to Use CI/CD
April 02, 2018 14:34
We use CircleCI to deploy to server. It is much easier than other websites like Travis especially for the free tier. It is especially useful for open source projects that need private access behind the scenes.
Easy to use
April 08, 2018 18:22
It help us with the automated build and test and also provide us with the build artifacts which we can use for the deployment also give use archive for each of our build, this things save us alot of time and cost
Full featured but hard to use
April 19, 2018 18:59
There's a lot of awesome features in CircleCI but it's generally hard to use and figure out. In addition, there seems to be some reliability issue, especially in connection with their third party dependencies.
Pinterest uses Jenkins
Jenkins is our continuous integration system for packaging builds and running unit tests after each check in.
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.
PMoelA uses Jenkins
Is for continuous integration and monitoring of the app - the app is deployed for test through Jenkins - dashboard for monitoring of status on GitHub, App health etc.
Goyoboard uses Jenkins
Continuous integration that run all test and build scripts, we separate it into few build stages for multiple sub-modules.
RocketFuel uses Jenkins
Jenkins is used for running tests before and after merge, for deploying changes and for running periodic tasks, similarly to cron.
tiferrei uses Jenkins
More customisable continuous integration, very useful for Swift compiling and PR management.
softwareantelope uses Jenkins
Continuous integration with built-in testing so every release is safe and any errors are picked up immediately.
Vinceveve uses Jenkins
Automating build, running specs, blocking pull request, deploy on the Kubernetes, Jenkins does this all with ease.
JimmyLv uses Jenkins
CI/CD, Jenkins 2.0
Clarabridge CX Social uses Jenkins
Used for continuous integration; e.g. running unit tests before deployment and of open GitHub Pull Requests.
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.
nickdecooman uses Jenkins
Experience with overall Jenkins configuration, setting up agents and (multi-branch) continuous deployment pipelines through Jenkinsfiles.
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.
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.
testim-tests uses Jenkins
We automate our release cycle and use it to trigger our tests once a new code was pushed
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.
skarfacegc uses Travis CI
To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel
saigkill uses Travis CI
Travis provides more than one Ruby version setting. So i can test my push directly in different Ruby versions.
LTE Consulting uses Travis CI
For GitHub integration, very easy to use and useful to get a confirmation that a build runs on a clean machine
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.
tiferrei uses Travis CI
Continuous integration for some of my iOS projects and open source frameworks
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).
Sud Web uses Travis CI
We use Travis CI to test and automatically deploy our static website on our server.
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.
Climate CoLab uses Travis CI
We use Travis CI to run our tests on each build and to build binaries used for deployments.
Virtually(Creative) uses Travis CI
Part of the automated build process, running any tests before deployment.
Pathwright uses CircleCI
Container-based CI service. Runs all of our backend tests, and is equipped to eventually run our client side tests.
Instacart uses CircleCI
We use CircleCI for our tests, but not for our builds. The builds are all manually triggered right now.
gregorynicholas uses CircleCI
continuous integration for mobile native ios builds, server deployments
Oomba uses CircleCI
CircleCI automatically runs all unit and e2e tests, as well as packaging and deploying builds to our live servers.
AngeloR uses CircleCI
We originally used CircleCI as our self-contained build system for our internal node modules. It was very easy to set up and configure. Unfortunately we ended up stepping away from it to Jenkins and then CodePipeline due to better integration with our various applications.
jflynn33 uses CircleCI
We prefer CircleCI because we care about testing our apps. We found it is better to invest the time writing rSPEC tests to ensure we don't insert any regression bugs with new branches. It's also nice to have a fully-automated deployment process from GitHub to Heroku.
PayParty uses CircleCI
We use Circle CI to do test and build automation. And also, do our deployments in stage and prod env.