TrustRadius
Travis CI is an open source continuous integration platform.https://dudodiprj2sv7.cloudfront.net/product-logos/09/xn/SBTU1TDCI1QE.JPEGOpen SourceWhy we use Travis CI2017-08-29T16:40:48.094ZWe use Travis CI for both our main app build and all the UI assets. It's set up to run on every commit, and a failed build will stop any merges to master.,Simple to set up.
Good documentation.
Clean interface.
Good level of customization.,Speed.
Job scheduling.
Integrations.,8,Saves time.
Software stability, visibility.
History.,Codeship,GitHub, Slack, TettraOscar MorrisonNo excuse to not write tests anymore!2017-02-07T16:10:38.408ZTravis CI has proven to be extremely valuable for projects with tight budgets or resources. It is very easy to define a variety of environments to run your test suite against, and its integration with your Git repo lets you test in parallel. Personally, I use GitHub, and when a test fails, the results show up directly in a pull request. It will also send me an email when tests fail, with all the details, and then again when tests pass again. Travis CI prevents you from having to install different environments and different versions locally and does so in an incredibly intuitive, and visually pleasing [way].,It is very simple to configure a range of environment versions and settings in a simple YAML file.
It integrates very well with Github, Bitbucket, or a private Git repo.
The Travis CI portal beautifully shows you your history and console logs. Everything is presented in a very clear and intuitive interface.,Travis CI is a fairly mature platform now, and most, if not all of the common complaints have been improved. This includes documentation and logs with color support.,10,Depending on the type of project, Travis CI can drastically reduce the need for QA resources.
Travis CI can be a very powerful part of your deployment pipeline.,Jenkins and CircleCI,Jenkins, GitHub, Atlassian Confluence, JIRA SoftwareRyan BrewsterThe best hosted CI service available, IMHO2017-01-27T15:27:39.506ZWe use Travis CI for the automation of builds of all pull requests so we can be sure all tests from our test suit are passing, before we start code review.Continuous integration of our projects, testing and automatically deploying into production upon successful merge of pull requests onto our master branches.,I love the ease of use, the UI is very simple and well thought out, and it is still powerful enough.
It integrates with Slack and keeps us informed of all build's status.
It is easy to integrate with Heroku for deployment once builds have passed all tests.,I think they could have a cheaper personal plan. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $69 a month for personal projects that I don't want to be open source.
There is no interface for configuring repos on Travis CI, you have to do it via a file in the repo. This make configuration very flexible, but also makes it harder for simpler projects and for small tweaks in the configuration.,10,It saves you in infrastructure and setup costs, since running a server and installing and maintaining Jenkins can be a hassle.,Eduardo SampaioGreat tool for TDD, CI and CD2017-01-23T15:07:59.189ZWe've been using Travis CI from day one. We believe continuous integration and continuous deployment are great ways to build a great product for our clients while keeping the quality standard high. Every feature we develop has its own set of tests, and if they fail in Travis CI, everyone's mission is to fix them as soon as possible so that we are back on track. As per the deployment process, we are releasing a new version of our API almost once a day. This is extremely easy if you have the assurance that Travis CI gives you.,Smooth integration with our GitHub account.
Test environment easy to configure.
Quick and useful notifications when build fails.,Integration with other repositories.
Support for other languages.,10,Software Quality is greatly influenced by Travis CI, as we detect problems very quickly with its help.
Time to Market for a new product is reduced as your deployment process is less complicated.
Release Train can be as rapid as once-per-day.,Jenkins, TeamCity and Codeship,GitHubMathias FonsecaDoesn't get any cheaper than "free" for open source projects2016-12-05T16:54:59.878ZI use the open source installation of Travis CI (https://travis-ci.org/jawnsy) for public GitHub projects. It's the de-facto continuous integration tool for public GitHub repositories, as it's free and works pretty well. It's used by a number of organizations that I'm a member of, including Kubernetes (https://github.com/kubernetes/kubernetes) and OpenShift (https://github.com/openshift/origin), though many larger projects also use Jenkins to provide a more customizable build environment. This can be useful for things like building Amazon Web Services AMIs, integration with external services that Travis doesn't support, etc.,It's simple and easy to get started (it can detect the language being used based on build configuration files like a Maven pom.xml).
It's free (as in beer) for open source projects.
It has a responsive staff (you can file issues on GitHub to ask for new languages or packages to be supported, and the turnaround time isn't too bad for the free offering).
The user interface is beautiful and easy-to-use, including features like live-tailing in-progress builds.
It supports specifying private environment variables and encrypted credentials, so that you can safely automate deployments (for example, pushing built docker images to DockerHub).,It only supports Linux and OS X, so other vendors (like AppVeyor) have to be used for Windows support.
The build matrices can be difficult to set up in the travis.yaml file.
Build queues can be long sometimes, since the open source offering has limited infrastructure. This problem does not affect the commercial offering, however.
Builds are limited to various versions of OS X and Ubuntu; other operating systems can be used for teh build via the Docker support.,10,It's improved my ability to deliver working code, increasing my development velocity.
It increases confidence that your own work (and those of external contributors) does not have any obvious bugs, provided you have sufficient test coverage.
It helps to ensure consistent standards across a team (you can integrate process elements like "go lint" and other style checks as part of your build).
It's zero-cost for public/open source projects, so the only investment is a few minutes setting up a build configuration file (hence the return is very high).
The .travis.yml file is a great way for onboarding new developers, since it shows how to bootstrap a build environment and run a build "from scratch".,AppVeyor, CircleCI, Drone and Jenkins,Gradle, Docker, Kubernetes, Apache MavenJonathan Yu, P.Eng.
Unspecified
Travis CI
22 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
