Travis CI
About Travis CI
Travis CI is a cloud-based continuous integration and delivery solution that helps small to large software development teams test, debug and deploy codes. The platform enables users to sync projects with the system to test multiple libraries against different runtime environments and data stores.
Travis CI uses OAuth to validate information for defining role-based access to repositories and facilitates lightweight directory access protocol (LDAP) or security assertion markup language (SAML) syncing for permissions. The solution also enables users to integrate TraviS CI with their existing GitHub enterprise installation in order to manage source code and scale out custom build infrastructure. It offers various customizable build environment images with languages and other dependencies for deploying different applications. Teams can increase their build capacity to test numerous codes.
Travis CI's multi-node setup and load balancer provides safety from hardware failures. It can be hosted on various cloud and on-premise environments such as AWS, Google Compute Engine, VMware, OpenStack, and Azure. Plus, it integrates with several third-party applications including TravisLight, Team Dashboard, Project Monitor, and more.
Images
Not sure about Travis CI?
Compare with a popular alternative
Starting Price
Pricing Options
Features
Integrations
Ease of Use
Value for Money
Customer Service
Alternatives
AWS Config
Ionic
Azure DevOps Server
TeamCity
Reviews
Already have Travis CI?
Software buyers need your help! Product reviews help the rest of us make great decisions.
- Industry: Internet
- Company size: 2–10 Employees
- Used Monthly for 2+ years
-
Review Source
Overall rating
- Value for Money
- Ease of Use
- Likelihood to recommend 10.0 /10
CI tool that has a lot of value for the money
Reviewed on 27/02/2020
I started using Travis initially because I needed a way to have consistent builds of our desktop...
I started using Travis initially because I needed a way to have consistent builds of our desktop software (built on Electron). Travis has just the tools I needed to make this happen. Doing local builds of the software was processor intensive, I had to go check the status of the build and I was always changing software on my local machine so sometimes builds would fail because I changed something. Travis has completely containerized build machines so you get the same result every time. We now use it for building all our software. I don't know what we'd do without it.
Pros
* Affordable (it's priced based on users/seats)
* Documentation is solid and easy to follow. I've never needed to contact support. There's good online Q&A since Travis has a large user base.
* Versatile (whatever software you're building, there's a recipe for it)
* Github integration : you get realtime build status RIGHT in Github which is awesome, once you get your system set up, you rarely ever visit Travis again. It just works.
Cons
There's really nothing I didn't like about Travis. Some of the quirks of Electron were the trickiest things to figure out, but that's not Travis's fault. There's a little learning curve when you go from building locally to building remotely with Travis where you need to understand how to set environment variables and retrieve those values in your config/script.
- Industry: Education Management
- Company size: Self Employed
- Used Daily for 2+ years
-
Review Source
Overall rating
- Value for Money
- Ease of Use
- Customer Support
- Likelihood to recommend 5.0 /10
Easy-to-use product but support for OSS failing
Reviewed on 02/02/2021
Pros
I like how easy it is to deploy and get up and running with this software and configuration files, etc (e.g. it's essentially just a commandline which is nice).
It was also really nice for all of my open-source projects while travis-ci.org was still running. I could deploy and have builds run without having to worry about money.
Cons
Ever since the move to travis-ci.com, support has been terrible and I've used up all of my free trial credits on my open-source web application's Cypress integration tests (https://github.com/tutorbookapp/tutorbook).
I contacted support 5 days ago and still haven't heard back about getting more open-source credits for my account. I seriously miss travis-ci.org (though I completely understand the problems with cryptocurrency mining, etc).
- Industry: Internet
- Company size: 2–10 Employees
- Used Daily for 2+ years
-
Review Source
Overall rating
- Ease of Use
- Likelihood to recommend 3.0 /10
Loved Travis in the past, sad to be on my way out.
Reviewed on 22/06/2021
Between the cons described above, the service degradation I've observed in the past 6 months and...
Between the cons described above, the service degradation I've observed in the past 6 months and your recent organizational and pricing changes (we are an open-source project and directly impacted), I'll be setting up Github actions to run my CI tests from here onwards (this is also about standardizing with other projects in my organization) and will deactivate my travis account.
Pros
It worked really nicely until about 6 months ago !
The previous unlimited open-source plan was generous, and a huge selling point.
Cons
Service has been less than ideal since the decision to move OSS projects travis-ci.org. We have felt this throttling of resources, and it was an indication that things were about tho change for the worse.
I was surprised to find that from one day to the next my CI builds weren't being run anymore.
Sure enough, you had a banner announcing the change from travis-ci.org to .com , but I didn't understand it would require changes on my side, and I didn't receive an email letting me know that my CI builds would just stop if I didn't manage it. I'll admit my fault in not checking more thoroughly.
Moving from .org to .com was not as easy as I would have liked (Why do I need to sign up for a beta? Why is it in beta, and why do you need more decisions from me that I don't have all the information to decide?), but I eventually got there.
- Industry: Information Technology & Services
- Company size: 2–10 Employees
- Used Daily for 1+ year
-
Review Source
Overall rating
- Value for Money
- Ease of Use
- Customer Support
- Likelihood to recommend 8.0 /10
CI / CD in a simple way
Reviewed on 02/02/2021
I'm very happy about Travis, until now I found always an answer for each need I had
I'm very happy about Travis, until now I found always an answer for each need I had
Pros
1. Documentation, maybe the most important value
2. Configuration flexibility in particular GIT SSH custom keys, env variables with sensitive information, build trigger (with inline configuration... very useful for testing configurations), machine SSH encrypted keys, configuration imports, custom scripts
3. Easy integration with GitHub
Cons
Permissions check (it's not so clear understand who can build, who can view build history, who can edit configuration).
Reasons for Switching to Travis CI
I already knew TeamCity but there wasn't a cloud version when I choosed Travis. Ionic has a ready to use mobile app configuration and we use it. I never had enough time to setup a Travis configuration build successfully a ionic app.- Industry: Research
- Company size: 5,001–10,000 Employees
- Used Monthly for 2+ years
-
Review Source
Overall rating
- Value for Money
- Ease of Use
- Likelihood to recommend 9.0 /10
Largely self-taught, test driven developer
Reviewed on 12/03/2021
It's the core, it's the standard, and it does work fairly well. I'm kind of surprised it isn't as...
It's the core, it's the standard, and it does work fairly well. I'm kind of surprised it isn't as straightforwardly automatic to sort from GitHub, and there are some confusing elements to enabling it (and I don't quite understand why it's not more integrated with GitHub actions but maybe I'm wrong on that) but it's the standard, and automating test suits is crucial to good, maintainable code (especially if maintained by a community).
Pros
It's free if your code is open source and lots of other services (like zenodo, netlify etc.) already sort out interoperability, usually a bit sooner than gitlab.
Cons
It might be a lot quicker/better maintained for non-free use, but the options for testing packages in R, for example, are kind of weak and very slow (assuming the examples I've come across are standard). The fact that they only include python2 by default, plus some permission issues means packages using reticulate (for python/R interoperability) have a bit of a pain to get going (and it takes a long time to test). I guess if default options could be better maintained that would be much appreciated.
Alternatives Considered
GitLabReasons for Switching to Travis CI
I didn't choose it, my employer did and to work with colleagues this was the only real option.Travis CI FAQs
Below are some frequently asked questions for Travis CI.Q. What type of pricing plans does Travis CI offer?
Travis CI offers the following pricing plans:
- Starting from: US$69.00/month
- Pricing model: Free Version, Subscription
- Free Trial: Available
Free for first 100 builds. Bootstrap - $69 per month. Startup - $129 per month. Small Business - $249 per month. Premium - $489 per month.
Q. Who are the typical users of Travis CI?
Travis CI has the following typical customers:
Self Employed, 2–10, 11–50, 51–200, 201–500, 501–1,000, 1,001–5,000
Q. What languages does Travis CI support?
Travis CI supports the following languages:
English
Q. Does Travis CI support mobile devices?
Travis CI supports the following devices:
Android (Mobile), iPhone (Mobile), iPad (Mobile)
Q. What other apps does Travis CI integrate with?
Travis CI integrates with the following applications:
GitHub, Project Monitor, User.com
Q. What level of support does Travis CI offer?
Travis CI offers the following support options:
Email/Help Desk, FAQs/Forum, Knowledge Base, Chat
Related categories
See all software categories found for Travis CI.
