Jenkins聽vs聽Strider聽vs聽Travis CI

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Jenkins
Jenkins

15.9K
12.6K
+ 1
2.1K
Strider
Strider

17
23
+ 1
11
Travis CI
Travis CI

4.8K
3.4K
+ 1
1.7K
- No public GitHub repository 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 Strider?

Strider is an Open Source Continuous Deployment / Continuous Integration platform. It is written in Node.JS / JavaScript and uses MongoDB as a backing store. It is published under the BSD license.

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.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Jenkins?
Why do developers choose Strider?
Why do developers choose Travis CI?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con

    Sign up to add, upvote and see more consMake informed product decisions

    Jobs that mention Jenkins, Strider, and Travis CI as a desired skillset
    What companies use Jenkins?
    What companies use Strider?
    What companies use Travis CI?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Jenkins?
    What tools integrate with Strider?
    What tools integrate with Travis CI?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Jenkins, Strider, and Travis CI?
      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.
      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.
      Bamboo
      Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
      Apache Maven
      Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.
      Puppet Labs
      Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
      See all alternatives
      Decisions about Jenkins, Strider, and Travis CI
      Jesus Dario Rivera Rubio
      Jesus Dario Rivera Rubio
      Telecomm Engineering at Netbeast | 10 upvotes 311.8K views
      atNetbeastNetbeast
      React Native
      React Native
      Android SDK
      Android SDK
      Objective-C
      Objective-C
      Travis CI
      Travis CI
      Bitrise
      Bitrise
      GitHub
      GitHub
      Firebase
      Firebase
      Amplitude
      Amplitude
      Intercom
      Intercom
      Mailjet
      Mailjet
      #SmartHome
      #End2end

      We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

      Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

      We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

      You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

      See more
      Tymoteusz Paul
      Tymoteusz Paul
      Devops guy at X20X Development LTD | 19 upvotes 866K views
      Vagrant
      Vagrant
      VirtualBox
      VirtualBox
      Ansible
      Ansible
      Elasticsearch
      Elasticsearch
      Kibana
      Kibana
      Logstash
      Logstash
      TeamCity
      TeamCity
      Jenkins
      Jenkins
      Slack
      Slack
      Apache Maven
      Apache Maven
      Vault
      Vault
      Git
      Git
      Docker
      Docker
      CircleCI
      CircleCI
      LXC
      LXC
      Amazon EC2
      Amazon EC2

      Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

      It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

      I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

      We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

      If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

      The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

      Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

      See more
      Joshua Dean K眉pper
      Joshua Dean K眉pper
      CEO at Scrayos UG (haftungsbeschr盲nkt) | 7 upvotes 80.4K views
      atScrayos UG (haftungsbeschr盲nkt)Scrayos UG (haftungsbeschr盲nkt)
      GitLab CI
      GitLab CI
      GitLab
      GitLab
      GitLab Pages
      GitLab Pages
      Jenkins
      Jenkins

      We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

      While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

      We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

      See more
      CircleCI
      CircleCI
      Travis CI
      Travis CI

      I initially chose CircleCI for a personal project because I was not satisified with using Travis CI in the past. When it came time to develop my CI/CD config on Circle, I was pleasantly surprised with the fantastic documentation, invaluable collection of example configs and helpful support provided. The free tier they provide is quite robust for most small projects and the platform is updated frequently with nice features.

      Areas where CircleCI could improve:

      • the UI is a bit slow (you can feel the local machine straining to load all the code) and it is not as intuitive as it could be
      • many UI elements receive updates and/or changes that are not always reflected in the current docs
      See more
      Travis CI
      Travis CI
      Appveyor
      Appveyor
      GitHub
      GitHub

      I recommend using Travis CI and/or Appveyor in all projects.

      Projects using these tools have given me confidence to know that I don't cause any breaking changes. Travis CI and Appveyor have functionality to test components of a project across multiple installation projects to ensure that modifications don't break a project. These tools integrate easily with GitHub and are useful in open source projects that must review contributions from many different people.

      See more
      Sebastian G臋bski
      Sebastian G臋bski
      CTO at Shedul/Fresha | 4 upvotes 320.6K views
      atFresha EngineeringFresha Engineering
      CircleCI
      CircleCI
      Jenkins
      Jenkins
      Git
      Git
      GitHub
      GitHub
      New Relic
      New Relic
      AppSignal
      AppSignal
      Sentry
      Sentry
      Logentries
      Logentries

      Regarding Continuous Integration - we've started with something very easy to set up - CircleCI , but with time we're adding more & more complex pipelines - we use Jenkins to configure & run those. It's much more effort, but at some point we had to pay for the flexibility we expected. Our source code version control is Git (which probably doesn't require a rationale these days) and we keep repos in GitHub - since the very beginning & we never considered moving out. Our primary monitoring these days is in New Relic (Ruby & SPA apps) and AppSignal (Elixir apps) - we're considering unifying it in New Relic , but this will require some improvements in Elixir app observability. For error reporting we use Sentry (a very popular choice in this class) & we collect our distributed logs using Logentries (to avoid semi-manual handling here).

      See more
      Tim Abbott
      Tim Abbott
      Founder at Zulip | 13 upvotes 78.5K views
      atZulipZulip
      Travis CI
      Travis CI
      CircleCI
      CircleCI

      We actually started out on Travis CI, but we've migrated our main builds to CircleCI, and it's been a huge improvement.

      The reason it's been a huge improvement is that Travis CI has a fundamentally bad design for their images, where they start with a standard base Linux image containing tons of packages (several versions of postgres, every programming language environment, etc). This is potentially nice for the "get builds for a small project running quickly" use case, but it's a total disaster for a larger project that needs a decent number of dependencies and cares about the performance and reliability of their build.

      This issue is exacerbated by their networking infrastructure being unreliable; we usually saw over 1% of builds failing due to transient networking errors in Travis CI, even after we added retries to the most frequently failing operations like apt update or pip install. And they never install Ubuntu's point release updates to their images. So doing an apt update, apt install, or especially apt upgrade would take forever. We ended up writing code to actually uninstall many of their base packages and pin the versions of hundreds of others to get a semi-fast, semi-reliable build. It was infuriating.

      The CircleCI v2.0 system has the right design for a CI system: we can customize the base image to start with any expensive-to-install packages we need for our build, and we can update that image if and when we want to. The end result is that when migrating, we were able to delete all the hacky optimizations mentioned above, while still ending up with a 50% faster build latency. And we've also had 5-10x fewer issues with networking-related flakes, which means one doesn't have to constantly check whether a build failure is actually due to an issue with the code under test or "just another networking flake".

      See more
      Jenkins
      Jenkins

      I'd recommend to go with Jenkins .

      It allows a lot of flexibility and additional plugins that provide extra features, quite often not possible to find elsewhere unless you want to spend time on providing that by yourself.

      One of key features are pipelines that allow to easily chain different jobs even across different repos / projects.

      The only downside is you have to deploy it by yourself.

      See more
      Google Cloud Build
      Google Cloud Build
      CircleCI
      CircleCI
      Travis CI
      Travis CI

      I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

      I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

      One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

      Feel free to checkout an example: Cloudbuild Example

      See more
      Interest over time
      Reviews of Jenkins, Strider, and Travis CI
      Avatar of tschellenbach
      CEO at Stream
      Review ofTravis CITravis CI

      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!

      How developers use Jenkins, Strider, and Travis CI
      Avatar of datapile
      datapile uses Travis CITravis 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).

      Avatar of Kalibrr
      Kalibrr uses JenkinsJenkins

      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.

      Avatar of Wirkn Inc.
      Wirkn Inc. uses JenkinsJenkins

      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.

      Avatar of B霉i Thanh
      B霉i Thanh uses JenkinsJenkins
      • 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.
      Avatar of P膿teris Caune
      P膿teris Caune uses Travis CITravis 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.

      Avatar of AngeloR
      AngeloR uses JenkinsJenkins

      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.

      Avatar of Trusted Shops GmbH
      Trusted Shops GmbH uses JenkinsJenkins

      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.

      Avatar of Dieter Adriaenssens
      Dieter Adriaenssens uses Travis CITravis 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.

      Avatar of Nate Ferrell
      Nate Ferrell uses Travis CITravis 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.

      Avatar of Andrew Williams
      Andrew Williams uses Travis CITravis CI

      To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel

      How much does Jenkins cost?
      How much does Strider cost?
      How much does Travis CI cost?
      Pricing unavailable
      Pricing unavailable
      News about Strider
      More news