Wir helfen Unternehmen in Deutschland
seit 15 Jahren bei der Softwareauswahl

Was ist Travis CI?

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

Das Continuous-Integration-Tool ist aus der Open-Source-Community hervorgegangen und wird sowohl von über 700.000 Community-Nutzer*innen als auch von multinationalen Unternehmen wie IBM, Zendesk, BitTorrent, Heroku, MOZ uvm. eingesetzt, um auf modernste Weise Software zu entwickeln und zu veröffentlichen.

Wer verwendet Travis CI?

Open-Source-Projekte und große Unternehmen gleichermaßen. Unternehmen wie IBM, Zendesk, Heroku, Moz, BitTorrent und viele andere vertrauen Travis CI.

Travis CI Software - 1
Travis CI Software - 2
Travis CI Software - 3
Travis CI Software - 4
Travis CI Software - 5

Du bist nicht sicher, ob Travis CI das Richtige ist? Mit einer beliebten Alternative vergleichen

Travis CI

Travis CI

4,1 (129)
69,00 $
Monat
Kostenlose Version
Kostenlose Testversion
22
3
3,9 (129)
3,9 (129)
3,3 (129)
VS.
Startpreis
Preisoptionen
Funktionen
Integrationen
Benutzerfreundlichkeit
Preis-Leistungs-Verhältnis
Kundenservice
45,00 $
Monat
Kostenlose Version
Kostenlose Testversion
34
8
4,1 (49)
4,3 (49)
4,3 (49)
Die grünen Bewertungsbalken geben an, welches Produkt gemessen an der Durchschnittsbewertung und der Zahl der Bewertungen am besten abschneidet.

Weitere gute Alternativen zu Travis CI

TeamCity
Am besten bewertete Funktionen
Kontinuierliche Bereitstellung
Unterstützt parallele Ausführung
Zugriffskontrollen / Berechtigungen
CircleCI
Am besten bewertete Funktionen
Kontinuierliche Bereitstellung
Kontinuierliche Lieferung
Unterstützt parallele Ausführung
Bitbucket
Am besten bewertete Funktionen
Quellkontrolle
Versionskontrolle
Zugriffskontrollen / Berechtigungen
Azure DevOps Server
Am besten bewertete Funktionen
Continuous Integration
Versionskontrolle
Zugriffskontrollen / Berechtigungen
Heroku
Am besten bewertete Funktionen
Einsatz-Management
Unterstützt zahlreiche Programmiersprachen
für Entwickler
Ionic
Am besten bewertete Funktionen
API
Benutzerdefinierte Entwicklung
Einsatz-Management
Azure DevOps Services
Am besten bewertete Funktionen
Continuous Integration
Kontinuierliche Bereitstellung
Werkzeuge zur Zusammenarbeit
Jenkins
Am besten bewertete Funktionen
Kontinuierliche Bereitstellung
Kontinuierliche Lieferung
Pipeline-Management
GitHub
Am besten bewertete Funktionen
Quellkontrolle
Werkzeuge zur Zusammenarbeit
Zugriffskontrollen / Berechtigungen

Bewertungen über Travis CI

Durchschnittliche Bewertung

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

Nutzerbewertungen nach Unternehmensgröße (Angestellte)

  • <50
  • 51-200
  • 201-1.000
  • >1.001

Bewertungen nach Punktzahl finden

5
47%
4
29%
3
17%
2
2%
1
5%
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!