Wir helfen Unternehmen in Deutschland
seit 15 Jahren bei der Softwareauswahl

Ü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)

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

In Betracht gezogene Alternativen:

Really simple to use continuous integration.

5,0 vor 5 Jahren

Vorteile:

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.

Nachteile:

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.

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.

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 letzten Monat Neu

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 3 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.

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!

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 3 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 3 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.

Griffith
Postdoc in UK
Forschung, 5.001–10.000 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

In Betracht gezogene Alternativen:

Largely self-taught, test driven developer

4,0 vor 3 Jahren

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

Vorteile:

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.

Nachteile:

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.

Jiří
Senior Software Quality Engineer in Tschechien
Computer-Software, 10.000+ Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

In Betracht gezogene Alternativen:

My OpenSource projects got accustomed to free CI; Travis is no longer that

4,0 vor 3 Jahren

Kommentare: I feel disappointed by the pricing change

Vorteile:

Established service; Easy to configure; Supports macOS and AArch64 Linux

Nachteile:

Pricing structure for free and Open Source projects

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 letztes Jahr

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.

Alex
Data Engineering Lead - SecureX in USA
Computer- & Netzwerksicherheit, 10.000+ Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Travis CI: One of our sharpest, most reliable, most powerful and transformative tools.

5,0 vor 3 Jahren

Kommentare: It's a daily productivity driver for our team. Incredibly valuable, reliable, and one of the best tools we have in our development process.

Vorteile:

I pushed hard for my team to build our CI/CD pipeline using Travis. It is just a tremendous tool, and I'm deeply grateful that we have this tool in our toolkit. [SENSITIVE CONTENT HIDDEN] said "If I had eight hours to chop down a tree, I’d spend the first six of them sharpening my axe." Travis CI is one of the sharpest tools we have, and it's made a massive difference in speeding up our team's productivity. You guys recently gave us the option to upgrade our private Travis CI to include even higher numbers of parallel builds, which made a massive difference to our ability to grow our development team, and to increase the rate at which we build our own software.

Nachteile:

For a while, we were working very hard on our end to try to figure out how to speed up our builds, and had to do quite a bit of work to try to optimize our software architecture to optimize around the limits on build concurrency in Travis. We made some progress on that, but it was slow going, and ultimately you gave us an option to pay for a higher degree of parallelism.

Denis
Co-Founder in Deutschland
Design, 2–10 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Good product, but very expensive

5,0 vor 3 Jahren

Kommentare: We are using Travis CI mostly for our products that have a PHP backend and a Angular PWA application. We are prerendering all pages in our CI process which, for some reason got really slow in the last 12-24 month. I dont know if Travis CI is limiting external HTTP requests (which we rely on to get the content to render). For example a project with 500 subpages takes 30minutes to render. We already checked our Backend endpoints and these are not the limiting factor. Running is locally is has a built time for around 5-6 minutes.

Vorteile:

I like the ease of deployments especially with multi-step-deploys of websites where the backend and frontend should be in sync.

Nachteile:

Only thing I need to complain is the pricing. For a small design and development agency like us the price of the "concurrent job"-based plan is way too expensive while our current credit-based plan (which i'm happy that this exist) is very often exceeded due to the nature of our deployments.

Pablo
Software developer in Argentinien
Finanzdienstleistungen, 201–500 Mitarbeiter
Verwendete die Software für: 6-12 Monate
Herkunft der Bewertung

Functional, but can be better

5,0 vor 3 Jahren

Kommentare: Honestly I can't say it is better than jenkins. I assume for the compay not having to deal with management and updates is an advantage, but from a user point of view is more or less the same thing. And jenkins blueocean looks way better.

Vorteile:

It works. Does what I expected. Not a fan.

Nachteile:

UI has lots of room for improvemente. As an example Logs screens are annoying, because the scroll hides the header. I only want to scroll the log , not the full screen. When I hover over a build I see a message like 'build #123 passed'. The build number does not tell me anything, it would way better to see the author and the message of the commit, it will save me a click Everywhere you have a commit you should see a tooltip with author/message, not just the link to github

Michael
Postdoctoral Researcher in USA
Forschung, 5.001–10.000 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Broken promises

1,0 vor 3 Jahren

Kommentare: Horrible. Broken promises. Unresponsive support. Will not use it, and I will aggressively move anyone I collaborate with off Travis as quickly as possible. Travis breaking the open-source infrastructure has already cost me days if not weeks of additional work.

Vorteile:

Before Travis got bought out and reneged on their promise to support open-source software, it was a cornerstone of my open source work. Alas, in its current form, I wouldn't touch Travis CI with a 10-foot pole. The only reason I still interact with it at all is that one of those projects is specifically for deploying documentation via Travis. As soon as I can move the project in a new direction, I'll be done with Travis for good.

Nachteile:

Travis broke their promise of supporting Open Source with free CI service. I requested OSS credits months ago and got no reply. It's not that the paid tiers are prohibitively expensive. In principle, I might be able to expense CI costs. However, Travis' actions have eroded any and all trust I might have had in them, so I would not do business with them at any level

Robert
Sr. Engineer in USA
Elektrische/elektronische Fertigung, 10.000+ Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

It's awful, but we are stuck with it

1,0 vor 3 Jahren

Kommentare: I hate using it, I never would have recommended it, I want our team off it as soon as possible but the one person that set it up refuses to look at anything else and has the bosses ear. So I'm stuck with this nightmare of a build system that is just AWFUL

Vorteile:

Nothing... I hate this platform. Gitlab is way better for CI/CD

Nachteile:

Everything, but mostly, debugging build issues and that build environments aren't cached from build to build and have to be completely rebuilt every time and for no reason seem to fail for random issues. Like not being able to download a dependency. Or failing to deploy to github releases without an helpful error messages. Or worse, saying you did deploy, but then the package is nowhere to be found, and there is no way to debug this

Patryk
Software Developer in Polen
Computer-Software, 51–200 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Recommendation

5,0 vor 3 Jahren

Vorteile:

It's easy to use and configure and also a nice user experience.

Nachteile:

It's expensive in comparison to other solutions

Ibraheem
FE dev in Deutschland
Sport, 11–50 Mitarbeiter
Verwendete die Software für: Mehr als 1 Jahr
Herkunft der Bewertung

why do i need a title? 🤔

5,0 vor 3 Jahren

Kommentare: very happy

Vorteile:

I like that it gives a pride option :D checking previous builds, who issues them and if the failed/passed is very nice. for the most part is is smooth and just does its job.

Nachteile:

finding out why a build failed is sometimes very annoying. scrolling a huge page of logs is not smooth (and maybe some better segmenting options there could be useful) we have a weekly recurring job that fails for linting reasons (but we still need it to run to get sonarQube coverage, idk if this is on us for bad implementation) but then who ever deployed last they get an email saying that the build failed. and we can only opt in or out from the whole thing and not just that type of builds.

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 3 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.

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 letztes Jahr

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.

Aashish
Software Engineer in USA
Computer-Software, 11–50 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Travis CI review

4,0 vor 2 Jahren

Vorteile:

This tool is best for mobile app automation. It supports native iOS, Android and other cross-platform like flutter.

Nachteile:

More number of builds are not supporter for a free/indie account.

Tom
self in Niederlande
Medienproduktion, Selbstständig
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Not much to say because it does everything I like.

5,0 vor 3 Jahren

Vorteile:

It does exactly what I need, and gets out of the way.

Nachteile:

I can't think of anything I'd improve. Perhaps a regular install of Python 3.8 and 3.9 without the matrix thing?

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 5 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.

Wechuli
Wechuli
Software Engineer in Kenia
Verifizierter Nutzer auf LinkedIn
Computer-Software, 1.001–5.000 Mitarbeiter
Verwendete die Software für: Mehr als 2 Jahre
Herkunft der Bewertung

Wonderful CI for Open-Source Projects

5,0 vor 4 Jahren

Kommentare: Travis CI is a great CI/CD tool that caters to most of my needs if am working for an open-source project.

Vorteile:

- Comprehensive documentation for almost all popular languages and deployment environments - Built-in plugins to cloud providers such as AWS, Google Cloud and Azure - Free for all open-source projects - Fairly easy to use and configure for almost all CI/CD scenarios.

Nachteile:

- It can be tricky to integrate with other online repositories other than GitHub such as Bitbucket. - You need to pay to support private builds.

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

David
David
Fullstack developer in Israel
Verifizierter Nutzer auf LinkedIn
Internet, 201–500 Mitarbeiter
Verwendete die Software für: Mehr als 1 Jahr
Herkunft der Bewertung

One of the better CI tools out there

5,0 vor 4 Jahren

Vorteile:

Very easy to set up, and out of the box gives me a lot of control over my deployments.

Nachteile:

It's more expensive compared to competing tools for smaller companies.