Wir helfen Unternehmen seit 18 Jahren,
bessere Software zu finden

Über Travis CI

Travis CI ermöglicht es Softwareentwicklungsteams, Ihren Code zuverlässig und nach modernsten Prozessen zu testen und zu deployen.

Erfahre mehr über Travis CI

Vorteile:

It does the job it is intended to do. For years I haven't had complaints until I had to deal with customer service.

Nachteile:

It can be tricky to integrate with other online repositories other than GitHub such as Bitbucket.

Bewertungen zu Travis CI

Durchschnittliche Bewertung

Benutzerfreundlichkeit
3,9
Kundenservice
3,3
Funktionen
4,2
Preis-Leistungs-Verhältnis
3,9

Weiterempfehlungsquote

6,9/ 10

Travis CI hat eine Gesamtbewertung von 4,1 von 5 Sternen basierend auf 129 Nutzerbewertungen auf Capterra.

Hast du Travis CI bereits verwendet?

Teile deine Erfahrungen mit anderen Softwareinteressenten.

Nutzerbewertungen filtern (129)

Shubham
Shubham
Cloud Engineer in Indien
Verifizierter Nutzer auf LinkedIn
Informationstechnologie & -dienste, 5.001–10.000 Mitarbeiter
Verwendete die Software für: 1-5 Monate
Herkunft der Bewertung

In Betracht gezogene Alternativen:

Travis CI - My Unstoppable open source integration platform.

4,0 vor 2 Jahren

Kommentare: my overall experience is moderate.

Vorteile:

What I like most is that it takes less time for configuration and It also supports a build matrix feature.

Nachteile:

What I like least is it provides limited support and have less customization options than Jenkins.

Verifizierter Rezensent
Verifizierter Nutzer auf LinkedIn
Internet, 5.001–10.000 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

The code integrates very well

4,0 vor 9 Monaten

Kommentare: It has been a very convenient experience, since I can easily see the status of my builds directly from the platform when logging in, it is exactly a good technical process for each build I need, it can be worked very easily in a group.

Vorteile:

Travis CI is a continuous integration tool that I find very useful as a Senior Software Development Engineer at [sensitive content hidden]. I love its ability to automate the entire process of building, testing, and deploying software. With Travis CI, I can be sure that any code changes I make will be seamlessly integrated with the main project and tested automatically.

Nachteile:

Integration with GitHub gives me a lot of errors, when logging in, when linking, when unlinking, that is quite tedious and only specialists on my team have found the solution.

Matthew
Project Lead in USA
Internet, 1.001–5.000 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Static matrices and changes to OSS terms mean I cannot recommend the product

3,0 vor 4 Jahren

Kommentare: Our initial years with Travis were successful, and we were quite happy with the product. But over time, the lack of flexibility meant struggling to create and deploy our CI definitions. But the part that killed Travis for us was the change to OSS terms late in 2020. We'd already noticed that our queues would become long, particularly if we had many contributors or maintainers working simultaneously. But with the changes in terms, we quickly ran into a scenario where we ran out of hours by mid-month. This left us with an untenable situation; as an OSS project, we have limited funds, and we would quickly run through those if we purchased a plan. As a result, we are within 1-2 weeks of moving off the platform entirely.

Vorteile:

When we first started using the product, it was one of the few that existed, and it provided us exactly the assurances we needed to have predictable, stable software releases. Idempotent runs made it possible to know exactly when and why something failed.

Nachteile:

Since we produce OSS libraries, it's important for us to test against each language version we support. Unfortunately, there is no way in Travis to dynamically create a matrix based on the library/package definition itself. For instance, we produce PHP libraries, and our package management solution, Composer, allows us to specify in the package the versions we support. Unfortunately, when we change those, we also need to remember to change the Travis definitions to reflect those changes. This becomes a source of error very quickly - Travis may report all is green, but it turns out we haven't added the new PHP version to the matrix, so it's a false sense of assurance. On top of that, it's impossible to succinctly make discrete jobs that do different things. For instance, I don't need to run coding standards checks, static analysis, and documentation linting for every single job in the matrix; I really only need to run these once. But to do that, Travis forces me to define env variables for jobs, and then use conditionals to determine what to run. This makes the CI definitions very convoluted, and, if you have a lot of repositories that need to do the same, hard to distribute when you have changes to make. Other CI systems address this.

Tamseel
Tamseel
Full stack JavaScript developer in Pakistan
Verifizierter Nutzer auf LinkedIn
Computer-Software, 11–50 Mitarbeiter
Verwendete die Software für: 6-12 Monate
Herkunft der Bewertung

In Betracht gezogene Alternativen:

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

4,0 vor 5 Jahren

Kommentare: 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.

Vorteile:

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.

Nachteile:

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.

James
DevOps Engineer in USA
Computer-Software, Selbstständig
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

In Betracht gezogene Alternativen:

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

4,0 vor 3 Jahren

Kommentare: 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.

Vorteile:

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.

Nachteile:

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!

Jason
CTO in USA
Computer-Software, 2–10 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

In Betracht gezogene Alternativen:

Pricing Changes, Botched Rollout

3,0 vor 4 Jahren

Kommentare: Overall, beyond the pricing switch, I had been very happy with Travis CI. But, after this pricing change without any notice, I have become unhappy with it. At $85/mo to build two projects without any concurrency (it's slow), I'm become less interesting in staying a customer.

Vorteile:

I liked the ease of use getting Travis setup, the caching, and the build matrix.

Nachteile:

I think the concurrency model is terrible. Sometimes when I want to deploy code to staging and production, I have to wait for each PR and commit to build before the push happens. Sometimes this takes 20 minutes for all branches to finish building before a push can happen. Also, I'm very unhappy with the pricing changes roll out. I have been paying for Travis for a couple years now. All of a sudden, my iOS team said they didn't think our builds were working any longer. There were a bunch of builds that didn't go through, saying we didn't have enough credits. Digging in, I realized your pricing model changed. So our builds have not been going through for close to a couple months now. I never received an email that you would be changing the pricing which would then break our builds. This to me is a botched roll out. You should have specifically told me that my iOS builds would stop working. In our dashboard, it just shows that our last build was successful 2 months ago. Not that no more builds were happening. This is unacceptable. So much so, that I am actually now reading the Travis CI to Circle CI migration document. Circle CI seems like a cheaper option for us now.

Raphael
Software developer in Deutschland
Computer-Software, 2–10 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

In Betracht gezogene Alternativen:

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

2,0 vor 4 Jahren

Kommentare: 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?

Vorteile:

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

Nachteile:

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.

Adam
Adam
Director of Information Technology in USA
Verifizierter Nutzer auf LinkedIn
Hochschulbildung, 10.000+ Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

In Betracht gezogene Alternativen:

Essential for software development

4,0 vor 4 Jahren

Kommentare: I am able to conduct a wide variety of tasks from checking compilers, running static analysis, and building documentation.

Vorteile:

Travis-CI was the first CI system I used on my research projects, and to this day Travis-CI still does the heavy lifting on most of my tests during Continuous Integration. It's extremely flexible; I have workflows that run static analysis, security checks, documentation builds, and more. The features and integrations with a number of other systems (GitHub, CodeCov, etc.) make this my go-to CI. I especially appreciate the support for Education customers, other CIs would be quite expensive by comparison.

Nachteile:

Operating systems support can lag. In particular, support for modern C++ compilers can be a bit tricky (it's an old item many of us have raised). The new plans price some organizations (e.g. Boost) out of using it. Support on the MacOS images is not as robust.

Francis
Francis
Research Software Developer in Kanada
Verifizierter Nutzer auf LinkedIn
Forschung, 51–200 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

In Betracht gezogene Alternativen:

review

5,0 vor 4 Jahren

Kommentare: It was amazing until the recent price changes.

Vorteile:

Very easy to setup and many integration examples. Multiple services and environments makes it quick to setup for many testing combinations.

Nachteile:

The pricing has gone up drastically recently and without that much time to adapt. The best way to keep services up and running without getting caught back-and-forth requests of build minutes was to move away from the service.

Verifizierter Rezensent
Verifizierter Nutzer auf LinkedIn
Computer-Software, 51–200 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Lots of features, sometimes build issues, a bit slow

3,0 vor 4 Jahren

Kommentare: It was a good choice at the time. But I am not sure if there are now better alternatives. I would especially check for a docker based build system.

Vorteile:

Travis has a lot of features which can be setup easily using configuration files. It is free for open source products and not to expensive for company projects.

Nachteile:

Quite often builds are stuck which leads to a huge stop in developments in hour company because we pretty much rely on it. Also the builds starts quite slow.

Verifizierter Rezensent
Verifizierter Nutzer auf LinkedIn
Informationstechnologie & -dienste, 1.001–5.000 Mitarbeiter
Verwendete die Software für: Mehr als 1 Jahr
Herkunft der Bewertung

Great tool for CI/CD

5,0 vor 2 Jahren

Vorteile:

Travis CI can be easily connected to a GitHub repository, making it easy to automate builds and deployments and guarantee the quality of the code with tests. It also has a big community that helps troubleshoot any issue.

Nachteile:

Travis CI does not offer dedicated build environments for the builds, which means that the builds are impacted by other builds running on the same shared infrastructure.

Eric
Software developer in Frankreich
Forschung, 2–10 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Hard to beat such an offer when in academia

5,0 vor 4 Jahren

Kommentare: The reproducibility trend is gaining momentum within the academical research community. CI usage, now a must have for software engineering concerns, can easily be stretched to address reproducibility issues and is thus being rapidly adopted.

Vorteile:

- navigating the smooth and complete interface (with a nice github integration) - logs are detailed, thorough and hosted for a long time - jobs don't get to wait for long delays once triggered - great (and generous) customer support - nothing to install on premises

Nachteile:

Every CI offer must face quite technical challenges to address specific/advanced services like dealing with credentials or managing sophisticated job workflows. Travis CI does the job quite nicely on such issues yet the learning curve can be quite steep at first. Yes, Travis CI does offer a thorough documentation, yet getting all the tidbits properly aligned can be a tedious task at first (your mileage may vary).

Verifizierter Rezensent
Verifizierter Nutzer auf LinkedIn
Computer-Software, 201–500 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Nice GitHub Integration

4,0 vor 4 Jahren

Vorteile:

I like that I can see the live status from GitHub and that the UI is very simple. I can easily find everything. The console output is colorized (it's not in other CI software I've used).

Nachteile:

Sometimes parts of log output is collapsed, which has hidden an error for me before. It took a while, but my team figured it out.

Tim
Senior Principal Software Engineer in USA
Informationstechnologie & -dienste, 1.001–5.000 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Customer service is terrible

3,0 vor 4 Jahren

Kommentare: Fine until I tried to talk with support.

Vorteile:

It does the job it is intended to do. For years I haven't had complaints until I had to deal with customer service...

Nachteile:

Customer service is terrible. Turn arounds are 24 hours are more. Responses are unhelpful and sometimes there's no response at all. My most recent experience involved trying to get a new hire access to our projects/org in Travis. He sent multiple emails back and forth with support, each time they said they'd fixed it and nothing had changed. Eventually he stopped getting responses. I also tried submitting a ticket and got no response at all.

Timothy
Software Development Team Lead in USA
Informationsdienst, 1.001–5.000 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

why is a title required?

3,0 vor 4 Jahren

Vorteile:

Its easy to use by default in new Ember web apps.

Nachteile:

All configuration goes in a single monolithic travis.yml file, and the syntax of this file is very mysterious. Understanding what a particular configuration does is difficult, and its difficult to figure out how to satisfy new requirements. In contrast, github actions allow for the separate configuration of many different workflows, and offer comparatively much better documentation. We mostly continue to use travis because we've already figured out how to configure it for our basic needs with a few projects, and our company has already purchased a plan. Its difficult to switch to another system, largely due to company politics.

Stéphane
Software architect in Frankreich
Telekommunikation, 10.000+ Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

New travis and chrome webdriver (java8 and java11)

3,0 vor 4 Jahren

Kommentare: I use travis for continouse integration and continous delivery of NoraUi Open source Framework

Vorteile:

multi compilation Oracle Java8, OpenJDK8, Oracle Java11, OpenJDK11, nodeJS, ...

Nachteile:

In new or last version of Travis-CI, I have often this error with the Chrome webdriver: "web view not found" My builds use 4 instances (Oracle Java8, OpenJDK8, Oracle Java11, OpenJDK11) and I still have several instances that do not go through because of this error; it is never the same who do not pass. by relaunching several times it can work.

Verifizierter Rezensent
Verifizierter Nutzer auf LinkedIn
Versicherung, 11–50 Mitarbeiter
Verwendete die Software für: Mehr als 1 Jahr
Herkunft der Bewertung

An awesome tool to handle autmatic testing with Github

5,0 vor 6 Jahren

Kommentare: overall a great tool for running CI tests automatically.

Vorteile:

Remove the manual work in running tests before merging code. Also it's scalable to multiple branches and developers. And it give viability on how the build is broken if any issues arise.

Nachteile:

1. A bit slow comparing to running the tests on local machine. 2. Have a verbose limitation of 4MB.

Verifizierter Rezensent
Verifizierter Nutzer auf LinkedIn
Computer-Software, 11–50 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Complex testing tool

5,0 vor 6 Jahren

Vorteile:

The free version have a good result and usability

Nachteile:

Somtimes it's hard to configure the test suite

Jacob
Senior Engineer in USA
Personalwesen, 11–50 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Does not integrate with Github any more

1,0 vor 4 Jahren

Kommentare: Does not work, no documentation of how team permissions are supposed to work.

Vorteile:

At first Travis CI was an easy-to-use way to run the test suite of our Ruby On Rails app when branches were pushed to GitHub. Then it locked me out of accessing the build results and just does not work any more.

Nachteile:

Github integration broke so I can no longer access the service, only 1 developer on my team can access it.

Olivier JM
Olivier JM
Software Developer in Sambia
Verifizierter Nutzer auf LinkedIn
Computer-Software, 2–10 Mitarbeiter
Verwendete die Software für: Mehr als 1 Jahr
Herkunft der Bewertung

Best Continuous Integration tool

5,0 vor 4 Jahren

Kommentare: I still use Travis CI in my opensource projects and it hasn't disappointed

Vorteile:

Travis It is free for opensource projects, beyond that Travis CI is pretty easy to setup just a few lines in the and you are good to go, it works with most third-party tools and allows you to do your custom jobs by running scripts in your CI configs

Nachteile:

I noticed that the caching doesn't work in most of the times and this might cause the jobs to take a bit of sometime.

Stephen
Senior Lecturer in Südafrika
Computer-Software, 11–50 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Great for Budding Software Engineers

5,0 vor 4 Jahren

Kommentare: Using Travis CI (educational plan) has helped my students to gain some real-world devops experience. It has allowed me, as an educator, to offer them this experience.

Vorteile:

I use Travis CI in my software engineering class so that my students can build and deploy to cloud-hosted websites. My students find it relatively easy to setup and use. As an educator I have oversight over all of my students' projects. I find the build history particularly useful as I can see how often builds are occurring and whether they are passing or failing. Ideally, projects should be built often and most builds should succeed. Travis CI really helps me to assess these aspects.

Nachteile:

There are no real cons that I can think of.

Praneet
developer in USA
Informationstechnologie & -dienste, 11–50 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Falling behind

3,0 vor 4 Jahren

Vorteile:

Everything listed in the Cons section? :)

Nachteile:

Lack of first-class support for build artifacts. The configuration format for a multi-stage pipeline isn't straightforward and a bit unusual among the competition. No support for 3rd-party extensions.

Verifizierter Rezensent
Verifizierter Nutzer auf LinkedIn
Internet, 2–10 Mitarbeiter
Verwendete die Software für: 6-12 Monate
Herkunft der Bewertung

Great option for testing - particularly for open source

5,0 vor 6 Jahren

Vorteile:

I have used Travis CI for open source software development for quite a while, and always found it to be reliable and easy to set up. The container-based approach makes the testing quick and repeatable, and the UI makes it very to see where your issues are. It also has brilliant integration with github, so that pull requests and branches can be tested independently, and results are shown right in the github UI.

Nachteile:

I've wanted to trial this in a commercial environment, and was disappointed by the lack of a free private tier to get started.

Carlo
Senior Frontend Developer in Deutschland
Computer-Software, Selbstständig
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Open Source Software

5,0 vor 4 Jahren

Vorteile:

I used to like your approach to give back to the open source community.

Nachteile:

That you changed your approach to giving back to the open source community.

Erik
Senior Database Programmer Clinical Trials in USA
Forschung, 201–500 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Switching to gh-actions

5,0 vor 4 Jahren

Kommentare: Very pleased with the product

Vorteile:

Works and integrates seemlessly. Love it.

Nachteile:

Pricing model has changed. I understand. We are open source and non-profit so moving away.