📅 最后修改于: 2021-01-04 03:05:30 🧑 作者: Mango
Jenkins和Travis CI用作持续集成(CI)工具，使开发人员可以在开发过程中集成代码分支，并对它们运行一系列自动化测试。它们都将耗时的手动构建，测试和部署软件任务转换为快速，自动化的过程。
在将Travis CI与Jenkins进行比较时，我们需要考虑我们的业务需求和预算。
Jenkins是使用Java编程语言编写的最受欢迎的开源自动化服务器。它促进了软件开发过程中持续集成和持续交付(CI / CD)的自动化过程。
Jenkins支持1400多种其他软件工具的插件。这些插件将Jenkins扩展到了五年。平台，UI，管理，源代码管理和构建管理。
Jenkins易于安装和使用。它提供了一个令人印象深刻的浏览器托管的项目管理仪表板。
评估和选择詹金斯的一些常见原因是：
Travis CI是第一个持续集成即服务工具。它引入了一种在云中构建代码的新方法。 Travis CI工具允许用户注册，链接其存储库，构建以及测试其应用程序。
该工具可以轻松地与常见的云存储库(如Bitbucket和GitHub)集成。它提供了许多自动CI选项，由于Travis CI服务器托管在云中，因此无需专用服务器。这使我们能够在不同环境，不同机器，不同操作系统上进行测试。
对于开源项目，Travis CI是免费的。对于商业项目，我们需要购买企业计划。
评估和选择Travis CI的一些原因包括：
以下是詹金斯和Travis CI之间的主要比较：
| Jenkins | Travis CI |
|---|---|
| Jenkins is a software tool that allows CI (Continuous Integration). | Travis CI is distributed CI service to test and build the project at GitHub. |
| It is mainly written in Java. | It is mainly written in Ruby. |
| It is developed by Sun Microsystems and originally called Hudson | Travis CI is developed by Travis CI community. |
| Jenkins has full system control. | It has very less system control. |
| Jenkins supports multiple version control systems like GIT and SVN. | Travis CI supports only GitHub version control. |
| It supports all platforms like Windows, Mac, Linux, etc. | It does not support Windows. It only supports Linux and Mac. |
| Many plugins are available for Jenkins. | Supports less plugins and use in Travis CI. |
| Website of Jenkins is Jenkins.io | The website of Travis CI is Travis.ci.org |
| Jenkins is free. But the development team need to run and maintain their dedicated server. This could be considered an extra expense. | Travis CI enterprise suites start at $129/month. Cost increase based on the level of required support. |
| It is an open-source free to use the tool. | It is commercial CI tool. |
| It is easy to use. | It is flexible to use. |
| It is good for GitHub. | It is excellent for GitHub. |
| It is a server-based tool. | It is a cloud-based tool. |
| It provides more customizations options. | It provides less customizations options. |
| Jenkins is highly scalable. | Travis CI is less scalable as compared to Jenkins. |
| Jenkins can be hosted internally. | Travis CI cannot be hosted internally. |
| Jenkins has a lot of resources, great community support, tutorials. | Travis CI has only community support and tutorials, fewer resources. |
| Jenkins is mainly used by the top companies. | Travis CI is used by good companies but yet to reach to great companies. |
| Jenkins is easy to install and make the service up and running with one command line. | Travis CI is easier to configure with .travis.yaml file. |
因此，通过上面的讨论，我们可以看到Travis CI和Jenkins都提供了出色的功能。但是，小型开源项目最适合Travis CI，因为它易于运行且设置迅速。另一方面，大型企业最适合詹金斯，因为它为私人项目提供免费许可，并提供广泛的可定制功能。因此，可以说这两种CI工具在其方式上都很不错。