Get Advice Icon

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

bitHound
bitHound

15
17
+ 1
22
Travis CI
Travis CI

4.9K
3.5K
+ 1
1.7K
Add tool

bitHound vs Travis CI: What are the differences?

bitHound: Continuous analysis for Node.js projects. Identify risks and priorities in your dependencies and code. With faster deployment cycles, a hundred competing priorities and tight deadlines to juggle– your team has a lot on their plate. Uncover and focus on the critical issues impacting your team, avoid software pitfalls and ship with confidence; Travis CI: A hosted continuous integration service for open source and private projects. 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.

bitHound and Travis CI are primarily classified as "Code Review" and "Continuous Integration" tools respectively.

Some of the features offered by bitHound are:

  • Do you know when your third party dependencies are at risk? bitHound gives you insight into the insecure, deprecated, outdated and unused packages impacting your software.
  • We analyze your code to help your team determine where focus is needed. Understand the mechanical issues impacting your codebase, reduce complexity and clutter, and gain insights that go beyond the command line with bitHound.
  • Whether it's formal issue management or the team's pending tech debt, it's important to get on top of these issues. bitHound offers an improved understanding of how the team is performing together and whether or not items are being left behind.

On the other hand, Travis CI provides the following key features:

  • Easy Setup- Getting started with Travis CI is as easy as enabling a project, adding basic build instructions to your project and committing code.
  • Supports Your Platform- Lots of databases and services are pre-installed and can simply be enabled in your build configuration, we'll launch them for you automatically. MySQL, PostgreSQL, ElasticSearch, Redis, Riak, RabbitMQ, Memcached are available by default.
  • Deploy With Confidence- Deploying to production after a successful build is as easy as setting up a bit of configuration, and we'll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, and CloudFoundry.

"Automatic dependency analysis" is the primary reason why developers consider bitHound over the competitors, whereas "Github integration" was stated as the key factor in picking Travis CI.

- No public GitHub repository available -
- No public GitHub repository available -

What is bitHound?

With faster deployment cycles, a hundred competing priorities and tight deadlines to juggle– your team has a lot on their plate. Uncover and focus on the critical issues impacting your team, avoid software pitfalls and ship with confidence.

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 bitHound?
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
    What companies use bitHound?
    What companies use Travis CI?

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

    What tools integrate with bitHound?
    What tools integrate with Travis CI?

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

    What are some alternatives to bitHound and Travis CI?
    ESLint
    A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
    SonarQube
    SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
    Code Climate
    After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.
    Prettier
    Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary.
    Codacy
    Codacy is an automated code review tool for Scala, Java, Ruby, JavaScript, PHP, Python, CoffeeScript and CSS. It's continuous static analysis without the hassle. Save time in Code Reviews. Tackle your technical debt
    See all alternatives
    Decisions about bitHound and Travis CI
    Jesus Dario Rivera Rubio
    Jesus Dario Rivera Rubio
    Telecomm Engineering at Netbeast · | 10 upvotes · 317.6K 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
    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
    Tim Abbott
    Tim Abbott
    Founder at Zulip · | 14 upvotes · 81.9K 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
    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 bitHound 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 bitHound 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 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 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

    Avatar of Sellsuki
    Sellsuki uses bitHoundbitHound

    Analyze Javascript source code and code quality.

    How much does bitHound cost?
    How much does Travis CI cost?
    News about bitHound
    More news