--- description: Travis CIを実際に使用したユーザーのレビューから、製品の機能や価格、メリットデメリットをご覧いただけます。類似製品との比較も簡単、ぴったりのSaaSが見つかるはず！ image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: Travis CIとは？ | 機能や料金、導入事例をご紹介【キャプテラ】 --- 現在地表示: [ホーム](/) > [CIツール](/directory/31119/continuous-integration/software) > [Travis CI](/software/179183/travis-ci) # Travis CI Canonical: https://www.capterra.jp/software/179183/travis-ci ページ：1 / 6\ 次へ: [次ページ](https://www.capterra.jp/software/179183/travis-ci?page=2) > ソフトウェア開発チームはTravis CIを使ってコードをテストし、自信を持ってデプロイできるようになります。 > > 評価：129人のユーザーによる評価は**4.1/5**。**おすすめ度**で最高の評価。 ----- ## 概要 ### Travis CIの対象ユーザー オープンソースのプロジェクトと大企業。Travis CIは、IBM、Zendesk、Heroku、Moz、BitTorrentなどの多くの企業から信頼を得ています。 ## 簡単な統計と評価 | 測定基準 | 評価 | 詳細 | | **総合評価** | **4.1/5** | 129 レビュー | | 使いやすさ | 3.9/5 | レビュー全体に基づく | | カスタマー・サポート | 3.3/5 | レビュー全体に基づく | | 価格の妥当性 | 3.9/5 | レビュー全体に基づく | | 機能 | 4.2/5 | レビュー全体に基づく | | おすすめ率 | 70% | (7/10 おすすめ度) | ## 企業情報 - **キャプテラについて**: IDERA - **設立**: 2011 ## ビジネスコンテキスト - **価格プラン**: $69.00 - **価格モデル**: (無料版が利用可能) (無料のトライアル) - **対象となる企業**: 自営業, 2～10, 11～50, 51～200, 201～500, 501～1,000, 1,001～5,000, 5,001～10,000, 10,000+ - **デプロイとプラットフォーム**: クラウド、SaaS、ウェブベース, Mac（デスクトップ）, Windows（デスクトップ）, Android（モバイル）, iPhone（モバイル）, iPad（モバイル） - **サポートされる言語**: 英語 - **利用可能な国**: アイスランド, アイルランド, アメリカ合衆国, アルバ, アルバニア, アンギラ, アンティグア・バーブーダ, アンドラ, イギリス, イタリア, インド, ウォリス・フツナ, ウクライナ, エストニア, エルサルバドル, オランダ, オーストラリア, オーストリア, オーランド諸島, カナダ さらに96件 ## 機能 - Automated Testing - コラボレーションツール - ダッシュボード - テスト管理 - デバッグ - バージョン管理 - リリース管理 - 品質保証 - 変更管理 - 継続的インテグレーション - 継続的デプロイ - 継続的デリバリ - 設定の管理 ## 統合 (合計3件) - GitHub - Project Monitor - User.com ## サポートのオプション - メール/ヘルプデスク - FAQ/フォーラム - ナレッジベース - チャット対応有 ## Category - [CIツール](https://www.capterra.jp/directory/31119/continuous-integration/software) ## 関連カテゴリー - [CIツール](https://www.capterra.jp/directory/31119/continuous-integration/software) - [DevOpsツール](https://www.capterra.jp/directory/31120/devops/software) ## 代替製品 1. [Jira](https://www.capterra.jp/software/19319/jira) — 4.4/5 (15314 reviews) 2. [GitHub](https://www.capterra.jp/software/129067/github) — 4.8/5 (6155 reviews) 3. [GitLab](https://www.capterra.jp/software/159806/gitlab) — 4.6/5 (1215 reviews) 4. [Bitbucket](https://www.capterra.jp/software/157785/bitbucket) — 4.6/5 (1343 reviews) 5. [AWS CloudFormation](https://www.capterra.jp/software/205397/cloudformation) — 4.5/5 (106 reviews) ## レビュー ### "Travis CI is great automation tool is easy to configure and run." — 4.0/5 > **Tamseel** | *2019年10月12日* | コンピュータ・ソフトウェア | おすすめ評価：9.0/10 > > **良いポイント**: 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. > > **改善点**: 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. > > 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. ----- ### "The code integrates very well" — 4.0/5 > **認証済みレビュアー** | *2024年5月13日* | インターネット | おすすめ評価：8.0/10 > > **良いポイント**: 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. > > **改善点**: 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. > > 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. ----- ### "Pricing Changes, Botched Rollout" — 3.0/5 > **Jason** | *2021年2月1日* | コンピュータ・ソフトウェア | おすすめ評価：4.0/10 > > **良いポイント**: I liked the ease of use getting Travis setup, the caching, and the build matrix. > > **改善点**: 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. > > 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. ----- ### "Travis CI: Great overall for over 8 years. Not anymore after travis-ci.COM migration & OSS credits" — 4.0/5 > **James** | *2021年9月8日* | コンピュータ・ソフトウェア | おすすめ評価：6.0/10 > > **良いポイント**: 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. > > **改善点**: 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\! > > 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. ----- ### "Essential for software development" — 4.0/5 > **Adam** | *2021年2月1日* | 高等教育 | おすすめ評価：7.0/10 > > **良いポイント**: 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. > > **改善点**: 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. > > I am able to conduct a wide variety of tasks from checking compilers, running static analysis, and building documentation. ----- ページ：1 / 6\ 次へ: [次ページ](https://www.capterra.jp/software/179183/travis-ci?page=2) ## リンク - [Capterraで表示する](https://www.capterra.jp/software/179183/travis-ci) ## このページは以下の言語で利用できます | ロケール | URL | | de | | | de-AT | | | de-CH | | | en | | | en-AE | | | en-AU | | | en-CA | | | en-GB | | | en-IE | | | en-IL | | | en-IN | | | en-NZ | | | en-SG | | | en-ZA | | | es | | | es-AR | | | es-CL | | | es-CO | | | es-CR | | | es-DO | | | es-EC | | | es-MX | | | es-PA | | | es-PE | | | fr | | | fr-BE | | | fr-CA | | | fr-LU | | | it | | | ja | | | nl | | | nl-BE | | | pl | | | pt | | | pt-PT | | | sv | | | tr | | ----- ## 構造化データ