此内容没有您所选择的语言版本。

13.7. Jenkins Continuous Integration


13.7.1. Introduction to Jenkins

The Jenkins cartridge integrates with OpenShift Enterprise applications to provide continuous integration by monitoring execution of repeated jobs. Visit http://jenkins-ci.org/ for more information about Jenkins.
The Jenkins client cartridge must be added to a new or existing application for it to build with Jenkins. After the Jenkins client cartridge is added to an application, the git push command initiates a build process inside Jenkins. For custom applications, or applications that have no upstream repositories, the build process is initiated directly from the Jenkins web interface rather than with the git push command.
There are a number of benefits that come with using Jenkins to build applications:
  • Archived build information
  • No application downtime during the build process
  • Failed builds are not deployed; instead, a previous working version is left in place
  • Additional memory and storage resources are available
  • A large community of Jenkins plug-ins
Jenkins can be used to build any number of applications, and is only limited by the number of available gears. For example, if a PHP application is created and MySQL database is on the first gear, then Jenkins is added to a separate gear. A third gear is used for the Jenkins builder. In other words, whenever the Jenkins builder is active, it occupies one of the available gears.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat