--- description: Reviews zu Travis CI Software: Systemübersicht, Funktionen, Preisinformationen und Ratings & Reviews. Entdecke kostenlose Live-Demos und vergleiche Travis CI mit ähnlichen Programmen. image: https://gdm-localsites-assets-gfprod.imgix.net/images/software_advice/og_logo-55146305bbe7b450bea05c18e9be9c9a.png title: Travis CI | Bewertungen, Preise und Demos – SoftwareAdvice DE --- Breadcrumb: [Startseite](/) > [DevOps Tools](/directory/4380/devops/software) > [Travis CI](/software/189256/travis-ci) # Travis CI Canonical: https://www.softwareadvice.de/software/189256/travis-ci Seite: 1 / 6\ Weiter: [Nächste Seite](https://www.softwareadvice.de/software/189256/travis-ci?page=2) > Travis CI ist eine cloudbasierte Plattform für fortlaufende Integration, die Entwicklungsteams dabei hilft, Projekte zu testen und die Produktion oder das Staging zu aktualisieren, wenn die Tests durchlaufen wurden. Zu den wichtigsten Funktionen gehören Authentifizierung, Änderungsmanagement, rollenbasierte Berechtigungen, Datensynchronisierung, fortlaufende Bereitstellung, nutzerdefinierte Entwicklung und Testmanagement. Teams, die Travis CI verwenden, können ihre Codes auf die Cloud-Plattform übertragen und erhalten durch die Integration des Systems in GitHub mehr Kontrolle über die Sicherheit. Die Lösung verwendet Authentifizierung über OAuth (Open Authorization), sodass Führungskräfte Nutzerberechtigungen synchronisieren können, um sicherzustellen, dass Teammitglieder nur auf die erforderlichen Verzeichnisse Zugriff haben. Vorgesetzte können SAML (Security Assertion Markup Language) und LDAP (Lightweight Directory Access Protocol) verwenden, um den Nutzerzugriff zu verwalten. Die Plattform nutzt eine Art 'Reinraum', der es Unternehmen ermöglicht, jeden Build in einer sauberen, neuen und konsistenten Umgebung auszuführen. > > Bewertung: **4.1/5** von 129 Nutzern. Top bewertet für **Weiterempfehlungsquote**. ----- ## Kurzstatistiken und Ratings | Metrik | Bewertung | Detail | | **Gesamt** | **4.1/5** | 129 Nutzerbewertungen | | Bedienkomfort | 3.9/5 | Auf Basis der Gesamtbewertungen | | Kundenbetreuung | 3.3/5 | Auf Basis der Gesamtbewertungen | | Preis-Leistungs-Verhältnis | 3.9/5 | Auf Basis der Gesamtbewertungen | | Funktionen | 4.2/5 | Auf Basis der Gesamtbewertungen | | Empfehlungsprozentsatz | 70% | (7/10 Weiterempfehlungsquote) | ## Über den Anbieter - **Unternehmen**: IDERA - **Gegründet**: 2011 ## Gewerblicher Kontext - **Startpreis**: 69,00 $ - **Preismodell**: (Kostenlose Version verfügbar) (Kostenlose Testversion) - **Zielgruppe**: Selbstständig, 2–10, 11–50, 51–200, 201–500, 501–1.000, 1.001–5.000, 5.001–10.000, 10.000+ - **Bereitstellungen und Plattformen**: Cloud, SaaS, webbasiert, Mac (Desktop), Windows (Desktop), Android (mobil), iPhone (mobil), iPad (mobil) - **Unterstützte Sprachen**: Englisch - **Verfügbare Länder**: Albanien, Amerikanisch-Samoa, Amerikanische Jungferninseln, Andorra, Anguilla, Antigua und Barbuda, Aruba, Australien, Bahamas, Barbados, Belarus, Belgien, Belize, Bermuda, Bosnien und Herzegowina, Brasilien, Britische Jungferninseln, Bulgarien, China, Cookinseln und 96 weitere ## Funktionen - API - Authentifizierung - Automated Testing - Berichterstattung / Analyse - Build-Protokoll - Continuous Integration - Dashboard - Datensynchronisation - Debuggen - Genehmigungs-Workflow - KPI-Überwachung - Konfigurationsmanagement - Kontinuierliche Bereitstellung - Kontinuierliche Lieferung - Prognosen - Qualitätssicherung - Release-Management - Rollen-basierte Genehmigung - Test-Management - Versionskontrolle ## Integrationen (3 insgesamt) - GitHub - Project Monitor - User.com ## Optionen für Kundensupport - E-Mail/Helpdesk - FAQ/Forum - Wissensdatenbank - Chat ## Category - [DevOps Tools](https://www.softwareadvice.de/directory/4380/devops/software) ## Ähnliche Kategorien - [DevOps Tools](https://www.softwareadvice.de/directory/4380/devops/software) - [Continuous-Integration-Tools](https://www.softwareadvice.de/directory/4694/continuous-integration/software) ## Alternativen 1. [GitHub](https://www.softwareadvice.de/software/397820/github) — 4.8/5 (6172 reviews) 2. [GitLab](https://www.softwareadvice.de/software/28004/gitlab) — 4.6/5 (1220 reviews) 3. [Datadog](https://www.softwareadvice.de/software/101405/datadog) — 4.6/5 (360 reviews) 4. [Octopus Deploy](https://www.softwareadvice.de/software/347094/octopus-deploy) — 4.8/5 (60 reviews) 5. [PyCharm](https://www.softwareadvice.de/software/207982/pycharm) — 4.7/5 (370 reviews) ## Nutzerbewertungen ### "CI tool that has a lot of value for the money" — 5.0/5 > **Ian** | *27. Februar 2020* | Internet | Empfehlungsbewertung: 10.0/10 > > **Vorteile**: \* 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. > > **Nachteile**: 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. > > 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. ----- ### "CI / CD in a simple way" — 5.0/5 > **EMANUELE** | *2. Februar 2021* | Informationstechnologie & -dienste | Empfehlungsbewertung: 8.0/10 > > **Vorteile**: 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 > > **Nachteile**: Permissions check (it's not so clear understand who can build, who can view build history, who can edit configuration). > > I'm very happy about Travis, until now I found always an answer for each need I had ----- ### "Static matrices and changes to OSS terms mean I cannot recommend the product" — 3.0/5 > **Matthew** | *28. Juni 2021* | Internet | Empfehlungsbewertung: 2.0/10 > > **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. > > 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. ----- ### "Largely self-taught, test driven developer" — 4.0/5 > **Griffith** | *12. März 2021* | Forschung | Empfehlungsbewertung: 9.0/10 > > **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. > > 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). ----- ### "My OpenSource projects got accustomed to free CI; Travis is no longer that" — 4.0/5 > **Jiří** | *9. Juli 2021* | Computer-Software | Empfehlungsbewertung: 5.0/10 > > **Vorteile**: Established service; Easy to configure; Supports macOS and AArch64 Linux > > **Nachteile**: Pricing structure for free and Open Source projects > > I feel disappointed by the pricing change ----- Seite: 1 / 6\ Weiter: [Nächste Seite](https://www.softwareadvice.de/software/189256/travis-ci?page=2) ## Links - [Auf SoftwareAdvice anzeigen](https://www.softwareadvice.de/software/189256/travis-ci) ## Diese Seite ist in den folgenden Sprachen verfügbar | Sprache | URL | | de | | | en | | | en-AU | | | en-GB | | | en-IE | | | en-NZ | | | fr | | ----- ## Strukturierte Daten