Jenkins权威指南：构建与管道自动化详解

需积分: 1 57 浏览量更新于2024-07-18 收藏 22.25MB PDF 举报

《Jenkins：权威指南》是一本深入探讨持续集成工具Jenkins的专业书籍，由John Ferguson Smart撰写，全面覆盖了Jenkins的核心概念、配置技巧以及高级实践。该书在2011年首次出版，旨在帮助读者理解和掌握如何有效地利用Jenkins进行软件开发过程中的自动化构建、测试和部署。书中涵盖了以下几个关键知识点： 1. **Jenkins简介**：Jenkins是一个开源的持续集成服务器，它通过构建生命周期管理来自动化软件开发流程。用户可以创建自定义的工作流（Pipeline），将代码提交、构建、测试和部署无缝集成在一起。 2. **安装与配置**：作者详细解释了如何在各种操作系统上安装Jenkins，并指导读者配置基础环境，如设置系统用户、插件安装以及安全设置，确保系统的稳定运行。 3. **构建管理**：书中介绍了如何创建和管理构建作业，包括配置构建触发器、构建步骤、构建后动作等，让读者了解如何实现自动化的代码构建流程。 4. **扩展与优化**：针对大型项目和分布式环境，书中涉及添加节点（slave nodes）和资源管理，以提高性能和并发处理能力。同时，读者也会学习如何优化Jenkins的性能和维护最佳实践。 5. **流水线（Pipeline）编程**：这是Jenkins的一大特色，书中展示了如何编写Dockerfile、GitLab CI/CD、Maven、Ant等工具的Pipeline脚本，实现从代码到部署的端到端自动化。 6. **插件和社区支持**：Jenkins拥有丰富的插件生态系统，作者会介绍如何利用这些插件增强功能，如测试报告、持续部署、CI/CD工具集成等，并强调社区在Jenkins发展中扮演的重要角色。 7. **实战案例分析**：书中提供了一些实际项目案例，让读者在理论学习的基础上，通过具体场景加深对Jenkins应用的理解和实践能力。《Jenkins：权威指南》不仅适合Jenkins新手入门，也是经验丰富的开发者提升技能、优化持续集成实践的必备参考资料。无论是希望搭建个人开发环境，还是在企业级项目中推广CI/CD文化，这本书都能提供扎实的基础知识和实用的指导。

So I was truly delighted that he took on the daunting task of writing a book about

Jenkins. It gives a great overview of the typical main ingredients of continuous inte-

gration. And for me personally, I always get asked if there’s a book about Jenkins, and

I can finally answer this question positively! But more importantly, this book reflects

his passion, and his long experience in teaching people how to use Jenkins, in combi-

nation with other things. But don’t take my words for it. You’ll just need to read on to

see it for yourself.

—Kohsuke Kawaguchi

Creator of the Jenkins project and Architect at CloudBees

xiv | Foreword

Preface

Audience

This book is aimed at relatively technical readers, though no prior experience with

Continuous Integration is assumed. You may be new to Continuous Integration, and

would like to learn about the benefits it can bring to your development team. Or, you

might be using Jenkins or Hudson already, and want to discover how you can take your

Continuous Integration infrastructure further.

Much of this book discusses Jenkins in the context of Java or JVM-related projects.

Nevertheless, even if you are using another technology stack, this book should give you

a good grounding in Continuous Integration with Jenkins. We discuss how to build

projects using several non-Java technologies, including as Grails, Ruby on Rails

and .NET. In addition, many topics, such as general configuration, notification, dis-

tributed builds and security are applicable no matter what language you are using.

Book Layout

Continuous Integration is like a lot of things: the more you put in, the more value you

will get out. While even a basic Continuous Integration setup will produce positive

improvements in your team process, there are significant advantages to gradually as-

similating and implementing some of the more advanced techniques as well. To this

end, this book is organized as a progressive trek into the world of Continuous Integra-

tion with Jenkins, going from simple to more advanced. In the first chapter, we start

off with a sweeping overview of what Jenkins is all about, in the form of a high-level

guided tour. From there, we progress into how to install and configure your Jenkins

server and how to set up basic build jobs. Once we have mastered the basics, we will

delve into more advanced topics, including automated testing practices, security, more

advanced notification techniques, and measuring and reporting on code quality met-

rics. Next, we move on to more advanced build techniques such as matrix builds, dis-

tributed builds and cloud-based CI, before discussing how to implement Continuous

Deployment with Jenkins. Finally, we cover some tips on maintaining your Jenkins

server.

Jenkins or Hudson?

As we discuss in the introduction, Jenkins was originally, and up until recently, known

as Hudson. In 2009, Oracle purchased Sun and inherited the code base of Hudson. In

early 2011, tensions between Oracle and the open source community reached rupture

point and the project forked into two separate entities: Jenkins, run by most of the

original Hudson developers, and Hudson, which remained under the control of Oracle.

As the title suggests, this book is primarily focused on Jenkins. However, much of the

book was initially written before the fork, and the products remain very similar. So,

although the examples and illustrations do usually refer to Jenkins, almost all of what

is discussed will also apply to Hudson.

Font Conventions

This book follows certain conventions for font usage. Understanding these conventions

up-front makes it easier to use this book.

Italic

Used for filenames, file extensions, URLs, application names, emphasis, and new

terms when they are first introduced.

Constant width

Used for Java class names, methods, variables, properties, data types, database

elements, and snippets of code that appear in text.

Constant width bold

Used for commands you enter at the command line and to highlight new code

inserted in a running example.

Constant width italic

Used to annotate output.

Command-Line Conventions

From time to time, this book discusses command-line instructions. When we do, out-

put produced by the console (e.g., command prompts or screen output) is displayed

in normal characters, and commands (what you type) are written in bold. For example:

$ ls -al

total 168

drwxr-xr-x 16 johnsmart staff 544 21 Jan 07:20 .

drwxr-xr-x+ 85 johnsmart staff 2890 21 Jan 07:10 ..

-rw-r--r-- 1 johnsmart staff 30 26 May 2009 .owner

-rw-r--r--@ 1 johnsmart staff 1813 16 Apr 2009 config.xml

drwxr-xr-x 181 johnsmart staff 6154 26 May 2009 fingerprints

drwxr-xr-x 17 johnsmart staff 578 16 Apr 2009 jobs

drwxr-xr-x 3 johnsmart staff 102 15 Apr 2009 log

drwxr-xr-x 63 johnsmart staff 2142 26 May 2009 plugins

xvi | Preface

-rw-r--r-- 1 johnsmart staff 46 26 May 2009 queue.xml

-rw-r--r--@ 1 johnsmart staff 64 13 Nov 2008 secret.key

-rw-r--r-- 1 johnsmart staff 51568 26 May 2009 update-center.json

drwxr-xr-x 3 johnsmart staff 102 26 May 2009 updates

drwxr-xr-x 3 johnsmart staff 102 15 Apr 2009 userContent

drwxr-xr-x 12 johnsmart staff 408 17 Feb 2009 users

drwxr-xr-x 28 johnsmart staff 952 26 May 2009 war

Where necessary, the backslash character at the end of the line is used to indicate a line

break: you can type this all on one line (without the backslash) if you prefer. Don’t

forget to ignore the “>” character at the start of the subsequent lines—it’s a Unix

prompt character:

$ wget -O - http://jenkins-ci.org/debian/jenkins-ci.org.key \

> | sudo apt-key add -

For consistency, unless we are discussing a Windows-specific issue, we will use Unix-

style command prompts (the dollar sign, “$”), as shown here:

$ java -jar jenkins.war

or:

$ svn list svn://localhost

However, unless we say otherwise, Windows users can safely use these commands from

the Windows command console:

C:\Documents and Settings\Owner> java -jar jenkins.war

or:

C:\Documents and Settings\Owner> svn list svn://localhost

Contributors

This book was not written alone. Rather, it has been a collaborative effort involving

many people playing different roles. In particular, the following people generously

contributed their time, knowledge and writing skill to make this a better book:

• Evgeny Goldin is a Russian-born software engineer living in Israel. He is a lead

developer at Thomson Reuters where he’s responsible for a number of activities,

some of which are directly related to Maven, Groovy, and build tools such as Ar-

tifactory and Jenkins. He has a vast experience in a range of technologies, including

Perl, Java, JavaScript and Groovy. Build tools and dynamic languages are Evgeny’s

favorite subjects about which he often writes, presents or blogs. These days he is

writing for GroovyMag, Methods & Tools and runs two open source projects of

his own: Maven-plugins and GCommons. He blogs at http://evgeny-goldin.com/

blog and can be found on Twitter as @evgeny_goldin.

Evgeny contributed a section on generating your Maven build jobs automatically

in Chapter 10.

Preface | xvii

• Matthew McCullough is an energetic 15 year veteran of enterprise software de-

velopment, open source education, and co-founder of Ambient Ideas, LLC, a Den-

ver consultancy. Matthew currently is a trainer for GitHub.com, author of the Git

Master Class series for O’Reilly, speaker at over 30 national and international con-

ferences, author of 3 of the top 10 DZone RefCards, and President of the Denver

Open Source Users Group. His current topics of research center around project

automation: build tools (Maven, Leiningen, Gradle), distributed version control

(Git), Continuous Integration (Jenkins) and Quality Metrics (Sonar). Matthew re-

sides in Denver, Colorado with his beautiful wife and two young daughters, who

are active in nearly every outdoor activity Colorado has to offer.

Matthew wrote the section on integrating Git with Jenkins in Chapter 5.

• Juven Xu is a software engineer from China who works for Sonatype. An active

member of the open source community and recognized Maven expert, Juven was

responsible for the Chinese translation of Maven: The Definitive Guide as well as

an original Chinese reference book on Maven. He is also currently working on the

Chinese translation of the present book.

Juven wrote the section on IRC notifications in Chapter 8.

• Rene Groeschke is a software engineer at Cassidian Systems, formerly known as

EADS Deutschland GmbH, as well as an open source enthusiast. A certified

ScrumMaster with about 7 years experience as a programmer in several enterprise

Java projects, he is especially focused on Agile methodologies like Continuous

Integration and Test-Driven Development. Besides his daily business, the Univer-

sity of Corporate Education in Friedrichshafen allows him to spread the word

about scrum and scrum related topics by giving lectures for the bachelor students

of information technology.

Rene contributed the section on building projects with Gradle in Chapter 5.

The Review Team

The technical review process for this book was a little different to the approach taken

for most books. Rather than having one or two technical reviewers read the entire book

near the end of the book writing process, a team of volunteers from the Jenkins com-

munity, including many key Jenkins developers, were able to read chapters as they were

written. This review team was made up of the following people: Alan Harder, Andrew

Bayer, Carlo Bonamico, Chris Graham, Eric Smalling, Gregory Boissinot, Harald

Soevik, Julien Simpson, Juven Xu, Kohsuke Kawaguchi, Martijn Verberg, Ross Rowe,

and Tyler Ballance.

xviii | Preface

剩余405页未读，继续阅读

arieslamb

粉丝: 2
资源: 5

Jenkins权威指南：构建与管道自动化详解

Jenkins：代码部署自动化宝典

Jenkins入门指南：从零到持续部署

Jenkins入门指南：自动化构建与持续集成实践

Jenkins The Definitive Guide

Jenkins The Definitive Guide 2011

jenkins-the-definitive-guide 英文pdf

jenkins-the-definitive-guide 英文文档

Cloud Foundry: The Definitive Guide

jenkins-the-definitive-guide:詹金斯读书笔记

Ant.The.Definitive.Guide2

最新资源