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.

Pricing starting from:

Not provided by vendor

  • Free Version
  • Free Trial
  • Subscription

Top 5 alternatives to Travis CI

Typical Customers

  • Freelancers
  • Small Businesses (2-50)
  • Mid-size Companies (51-500)
  • Large enterprises (500 and more)

Deployment

  • Cloud-based
  • On-premise

Markets

Andorra, Antigua & Barbuda, Anguilla, Albania, Curaçao , American Samoa, Austria, Australia, Aruba, Åland Islands, Bosnia & Herzegovina, Barbados, Belgium, Bulgaria, Bermuda, Brazil, Bahamas, Belarus, Belize, Canada, Switzerland, Cook Islands, China, Costa Rica, Cuba, Cyprus, Czechia, Germany, Denmark, Dominica, Dominican Republic, Estonia, Spain, Finland, Fiji, Micronesia, Faroe Islands, France, United Kingdom, Grenada, Guernsey, Gibraltar, Greenland, Guadeloupe, Greece, Guatemala, Guam, Honduras, Croatia, Haiti, Hungary, Ireland, Isle of Man, India, Iceland, Italy, Jersey, Jamaica, Japan, Kiribati, St Kitts & Nevis, Cayman Islands, St Lucia, Liechtenstein, Lithuania, Luxembourg, Latvia, Monaco, Moldova, Montenegro, St Martin, Marshall Islands, North Macedonia, Northern Mariana Islands, Martinique, Montserrat, Malta, Mexico, New Caledonia, Norfolk Island, Nicaragua, Netherlands, Norway, Nauru, New Zealand, Panama, French Polynesia, Papua New Guinea, Poland, St Pierre & Miquelon, Puerto Rico, Portugal, Palau, Romania, Serbia, Russia, Solomon Islands, Sweden, Slovenia, Svalbard & Jan Mayen, Slovakia, San Marino, El Salvador, Turks & Caicos Islands, Tonga, Turkey, Trinidad & Tobago, Tuvalu, Ukraine, United States, Vatican City, St Vincent & the Grenadines, British Virgin Islands, US Virgin Islands, Vanuatu, Wallis & Futuna, Samoa

Supported Languages

English

Pricing starting from:

Not provided by vendor

  • Free Version
  • Free Trial
  • Subscription

Top 5 alternatives to Travis CI

Images

Travis CI Software - Travis CI insights screenshot
Travis CI Software - Travis CI build screenshot
Travis CI Software - Travis CI codes screenshot
Travis CI Software - Travis CI personal access tokens screenshot
Travis CI Software - Travis CI web hooks screenshot
View 6 more
Travis CI video
Travis CI Software - Travis CI insights screenshot
Travis CI Software - Travis CI build screenshot
Travis CI Software - Travis CI codes screenshot
Travis CI Software - Travis CI personal access tokens screenshot
Travis CI Software - Travis CI web hooks screenshot

Features

Total features of Travis CI: 22

  • API
  • Access Controls/Permissions
  • Approval Workflow
  • Authentication
  • Automated Testing
  • Build Log
  • Change Management
  • Collaboration Tools
  • Configuration Management
  • Continuous Delivery
  • Continuous Deployment
  • Continuous Integration
  • Dashboard
  • Data Synchronization
  • Debugging
  • KPI Monitoring
  • Projections
  • Quality Assurance
  • Release Management
  • Reporting/Analytics
  • Role-Based Permissions
  • Testing Management

Alternatives

Heroku

4.6
#1 Alternative to Travis CI
Heroku is a cloud platform as a service (PaaS) designed for developers and teams to build, deliver, monitor, and scale...

GitLab

4.6
#2 Alternative to Travis CI
GitLab is an integrated, open source DevOps lifecycle management platform for software development teams to plan, code,...

AppVeyor

0
#3 Alternative to Travis CI
AppVeyor is a continuous integration software designed to help businesses build, test, and deploy applications across...

Bitbucket

4.6
#4 Alternative to Travis CI
Bitbucket is a Git solution for teams, which allows users to collaborate on code with inline comments and code review,...

Reviews

Overall rating

4.1 /5
(126)
Value for Money
3.9/5
Features
4.1/5
Ease of Use
3.9/5
Customer Support
3.3/5

Already have Travis CI?

Software buyers need your help! Product reviews help the rest of us make great decisions.

Showing 5 reviews of 126
Elliott
Overall rating
  • Industry: Computer Software
  • Company size: 11-50 Employees
  • Used Daily for 2+ years
  • Review Source

Overall rating

  • Value for Money
  • Ease of Use
  • Customer Support
  • Likelihood to recommend 10.0 /10

Really simple to use continuous integration.

Reviewed on 18/07/2019

Pros

We use it to run php unit tests whenever we commit code to a repository. All we have to do is include a file in the root of the project and enable the project in the travis interface. Takes less than 5 minutes to set up fully automated unit testing. Much more easy than setting up your own CI pipeline with the huge amount of different apps that exists. Generous free tier.

Cons

Can be slow at times, documentation can on occasion be more minimal than I would like. As a developer you get used to this though, there are always loads of examples online.

Alternatives Considered

GitLab

Reasons for Switching to Travis CI

Travis works on all major providers.
Tamseel
Overall rating
  • Industry: Computer Software
  • Company size: 11-50 Employees
  • Used Weekly for 6-12 months
  • Review Source

Overall rating

  • Value for Money
  • Ease of Use
  • Customer Support
  • Likelihood to recommend 9.0 /10

Travis CI is great automation tool is easy to configure and run.

Reviewed on 12/10/2019

We have used Travis ci for automation of code building, testing and deployment. Travis CI is one of...

We have used Travis ci for automation of code building, testing and deployment. Travis CI is one of the top continuous integration and continuous delivery tool available in the market. We usually use Travis CI for medium scale projects because it easy to use, few minutes of configure is needed comparative to Jenkins which require skilled professional to configure it. We have used it for test projects as it is free for public projects.
Travis Ci is good for small to medium scale projects, which doesn’t require much of the customization or less complex projects. Travis CI is also good for public and open source projects because it provides free tier for public projects. It’s easy to use, you don’t need any professional skill to set it up.

Pros

Great thing about Travis CI is it’s easy to use, easy to configure and start running it, you can easily integrate GitHub account and whenever you push your code its integrated and tested on Travis CI. Travis CI doesn’t need hosting server to run it unlike Jenkins which require hosting server. For public projects you don’t have to pay, its free to use for you test and open source projects. Testing on different environment, devices, OS is optimized and run synchronously. You don’t have to maintain software updates for Travis CI unlike Jenkins. It is fast for testing code on different environment by having different jobs like you can have separate job for unit testing and separate jobs for integration testing.

Cons

Travis CI doesn’t have that much flexibility respect to customization as compare to Jenkins. Integration with third-party tools is not too much which reduces it flexibility. You code is accessible to Travis CI which is not good for most sensitive projects. You must pay for private projects as comparative to Jenkins which is free for private projects.

Alternatives Considered

CircleCI and Jenkins

Reasons for Choosing Travis CI

Jenkins require lot of configuration to set it up which require extra time that's why Jenkins is not good for small scale projects. We still use Jenkins for large scale project in that case Jenkins gives lot of flexibility of customization.

Reasons for Switching to Travis CI

Travis require less time to configure and it doesn't require hosting server to host it. Online community support is good too.
Aldo
Overall rating
  • Industry: Education Management
  • Company size: 201-500 Employees
  • Used Daily for 1+ year
  • Review Source

Overall rating

  • Value for Money
  • Ease of Use
  • Customer Support
  • Likelihood to recommend 8.0 /10

Review for Travis

Reviewed on 19/10/2022

Pros

I like the ease to setup the CI for automating the deployments in the different applications

Cons

probably the cost if you can start to use it and don't have an idea of estimate cost

Alternatives Considered

Jenkins

Reasons for Switching to Travis CI

for use the open source applications
Raphael
Overall rating
  • Industry: Computer Software
  • Company size: 2-10 Employees
  • Used Daily for 2+ years
  • Review Source

Overall rating

  • Value for Money
  • Ease of Use
  • Customer Support
  • Likelihood to recommend 1.0 /10

Used to be one of the only good option, not so much more today

Reviewed on 10/02/2021

We see it here as less and less professional. It started with a lot of time to get new images, the...

We see it here as less and less professional. It started with a lot of time to get new images, the problem of running after 4PM (Berlin time), the cache for ccache that suddenly disappear (which makes us use even more credits, obviously), and we are missing more and more CD.

It really feels as if, after Travis was bought, that the board decided to "cash in" money. You even need to pay credits now for OSS? How is that supporting it?

Pros

I liked the ease to setup a new project with it, once you know how to get around the product.

Cons

For sure this new price plan, that was announced a day *after* it was put in place (seriously?).
It costs us more than half of the credits to make just one build. The price per minute is just insane. I can have more workers and unlimited build times with Azure DevOps, for about the same amount of money of just the subscription alone (so not counting those Travis add-ons).

When the credits are done, then the CI will just block. You need to close and reopen the PR. Problem is that we have other GitHub integrations, so this makes the process really painful.

Alternatives Considered

Jenkins and AppVeyor

Reasons for Choosing Travis CI

General maintenance time was too high for our small team.

Reasons for Switching to Travis CI

We are actually also using AppVeyor. We didn't choose over Jenkins as it seemed it would still imply too much maintenance time (infrastructure and devop)
James
Overall rating
  • Industry: Computer Software
  • Company size: Self Employed
  • Used Monthly for 2+ years
  • Review Source

Overall rating

  • Value for Money
  • Ease of Use
  • Customer Support
  • Likelihood to recommend 6.0 /10

Travis CI: Great overall for over 8 years. Not anymore after travis-ci.COM migration & OSS...

Reviewed on 08/09/2021

Overall, Travis CI used to be the best turnkey solution for independent Open Source developers to...

Overall, Travis CI used to be the best turnkey solution for independent Open Source developers to set up Continuous Integration and Unit Testing pipelines. Thanks to bad actors such as unscrupulous bitcoin miners, this once great free open source community service has been morphed into a paid credit-based system. Lack of customer support responses have pushed independent volunteer open source developers out. We simply cannot afford CI testing when our software is free and open source by design.

Pros

As a long-time user of TravisCI for 8 years, I loved the ease of setting up CI testing pipelines and testing matrices with a single .travis.yml file. It made testing DevOps Chef cookbooks easy and was a great solution that integrated well with test-kitchen.

Cons

When getting a remote VM testing pipeline set up, there are some barriers to ease of debugging. This was primarily due to the lack of live SSH terminal access to poke around at the testing environment to debug job failures. After they added Debug Mode, this became a bit easier.

The main problem with Travis-CI was recently introduced with the travis-ci.COM migration. Users were encouraged to migrate projects over to the new website with no way of going back. A new paid credits system was forcibly implemented, with some promise of Open Source credits. All of my projects on TravisCI were free and OSS licensed, so I asked for OSS credits. After a few back and forth emails, I was promised 25k credits. However, after checking in the OSS credits section I still see zero credits listed.

It seems that just like that, Travis CI was taken away from OSS users who chose to migrate with no warning about the implications. Travis CI news blog posts explain that this change was made due to some nefarious bitcoin miners abusing their free build systems to mine cryptocurrency. So just like in school where the bad apple ruins it for the rest of the class, now Travis CI has been taken away from small Open Source developers.

Please improve your customer support and reinstate OSS credits for independent Open Source developers! Any kind of response or clarity around the application process would be much appreciated!

Alternatives Considered

CircleCI and Jenkins

Reasons for Switching to Travis CI

I used to love the ease of setting up a Travis CI pipeline for Open Source projects. Now there are artificial barriers to doing so.
Showing 5 reviews of 126 Read all reviews

Travis CI FAQs

Below are some frequently asked questions for Travis CI.

Travis CI offers the following pricing plans:

  • Starting from:
  • 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.

Travis CI has the following typical customers:

Self Employed, 2-10, 11-50, 51-200, 201-500, 501-1,000, 1,001-5,000

Travis CI supports the following languages:

English

Travis CI supports the following devices:

Android (Mobile), iPhone (Mobile), iPad (Mobile)

Travis CI integrates with the following applications:

GitHub, Project Monitor, User.com

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.