詹金斯搭建
In the previous chapter, we studied the concept of "Continuous integration" aka "CI". In order to create an environment for a project with CI enabled, a tool is required for the same. Hence, Jenkins jumps into the action. Jenkins is an open source tool to make the continuous integration.
在上一章中,我们研究了“连续集成”(也称为“ CI”)的概念。 为了为启用了CI的项目创建环境,需要使用相同的工具。 因此,詹金斯跳槽了。 Jenkins是进行持续集成的开源工具。
Jenkins was the project which was forked from Hudson due to some issues with the Oracle. Jenkins is basically a server based system running in a servlet container which is nothing but the apache tomcat. It supports many tools like Git, SVN, Mercurial and Clearcase. Jenkins was primarily started by a developer called Kuhsoke Kawaguchi.
由于Oracle的某些问题,Jenkins是从Hudson分叉的项目。 Jenkins基本上是一个运行在servlet容器中的基于服务器的系统,该容器不过是apache tomcat。 它支持许多工具,例如Git,SVN,Mercurial和Clearcase。 Jenkins主要由名为Kuhsoke Kawaguchi的开发人员启动。
詹金斯做什么? (What Jenkins does?)
The primary job of the Jenkins is to execute a list of steps configured which is based on a trigger. Below are the list of steps/tasks performed by Jenkins when triggered :
Jenkins的主要工作是执行基于触发器配置的步骤列表。 下面是Jenkins触发时执行的步骤/任务的列表:
Perform the code compilation & build the software with ANT, Maven or Gradle.
执行代码编译并使用ANT,Maven或Gradle构建软件。
Run an internal shell script
运行内部Shell脚本
Archive the resultant builds
存档生成的构建
At last start the execution of the integration tests.
最后,开始执行集成测试。
Monitoring the execution of the above tasks.
监视以上任务的执行。
Provision to stop the build in case of failure in any of the steps.
在任何步骤出现故障时都可以停止构建。
Notifying the user about the success or failure of each build.
通知用户每个构建的成功或失败。
詹金斯关注什么? (What Jenkins focuses on?)
Jenkins mainly focuses on 2 important activities :
詹金斯(Jenkins)主要关注以下两项重要活动:
Continuous build of the software : Nothing but the creating a continuous integration environment
持续构建软件:创建持续集成环境无非
Monitoring execution of external jobs : This monitors the jobs defined - CRON jobs.
监视外部作业的执行:监视定义的作业-CRON作业。
詹金斯的特点 (Features of Jenkins)
Easy to install & configure.
易于安装和配置。
Permanent link - readable URLs for the build details.
永久链接-生成详细信息的可读URL。
Email integration for notifications.
电子邮件集成的通知。
JUnit tests reporting.
JUnit测试报告。
Tagging support for every successful builds.
标记支持每个成功的构建。
Distributed builds.
分布式构建。
File fingerprinting for managing dependencies
文件指纹识别,用于管理依赖项
Plugin support
插件支持
詹金斯最佳做法 (Jenkins Best Practices)
Below are the list of some best practices to be made while working with Jenkins :
以下是与Jenkins合作时应采取的一些最佳做法的列表:
Always secure Jenkins - user authentication.
始终确保Jenkins的安全-用户身份验证。
Use file fingerprinting to manage dependencies.
使用文件指纹管理依赖项。
Integrate Jenkins with the issue tracking systems like JIRA.
将Jenkins与JIRA等问题跟踪系统集成。
Always configure Jenkins to generate a trend report.
始终将Jenkins配置为生成趋势报告。
Setup Jenkins on a partitioned space where the disk space is more.
在磁盘空间更多的分区空间上安装Jenkins。
Setup different jobs for maintenance and development projects.
为维护和开发项目设置不同的作业。
Archive unused jobs before deleting them.
在删除未使用的作业之前,请对其进行存档。
Setup email notification to all the developers of the team.
设置向团队所有开发人员的电子邮件通知。
Tag, Branch, Baseline after each successful build.
每次成功构建后,标记,分支,基准。
翻译自: https://www.studytonight.com/jenkins/jenkins-integration-server
詹金斯搭建