Jenkins-在docker中的持续集成

流程设计

一、安装Jenkins

docker安装请移步《还不会安装docker？这里帮你搞定》。
docker-compose安装请移步《Harbor-企业级docker私服管理》。

• 拉jenkins镜像
  建议拉2.251版本，因为安装插件时，很多插件不支持低版本的jenkins安装。

$ docker pull jenkins/jenkins:2.251

打标签：

$ docker tag jenkins/jenkins:2.251 192.168.0.150:9000/oa/jenkins:2.251

登录：

$ docker login 192.168.0.150:9000

推送到docker私服：

$ docker push 192.168.0.150:9000/oa/jenkins:2.251

编写docker-compose.yml文件：

version: '3'
services:
  jenkins:
    container_name: jenkins
    hostname: 192.168.0.150
    image: 192.168.0.150:9000/oa/jenkins:2.251
    restart: always 
    privileged: true
    environment:
       TZ: 'Asia/Shanghai'
    volumes:
      - "/var/jenkins_home:/var/jenkins_home"
      - "/var/run/docker.sock:/var/run/docker.sock"
      - "/root/download/apache-maven-3.5.4:/usr/local/maven"
    ports:
      - "7000:8080"

在docker-compose.yml目录生成并启动docker容器（-d表示后台运行）：

$ docker-compose up -d

由于自带插件下载网站太慢，所以需要设置加速：

$ cd /var/jenkins_home/updates/
$ vim default.json

:1,$s/http:\/\/updates.jenkins-ci.org\/download/https:\/\/mirrors.tuna.tsinghua.edu.cn\/jenkins/g

替换连接测试url:

:1,$s/http:\/\/www.google.com/https:\/\/www.baidu.com/g

进入vim先按esc再输入输入“：”，然后再粘贴上边的：后边的命令，注意不要写两个冒号！

在docker-compose.yml目录执行命令停止并删除容器：

$ docker-compose down

重新启动：

$ docker-compose up -d

等待启动成功。

二、安装JDK

$ yum install java-1.8.0-openjdk-devel

查看jdk版本：

$ java -version

三、安装maven

下载maven:
http://mirrors.hust.edu.cn/apache/maven/maven-3/3.5.4/binaries/

解压到/root/download:

$ tar -zxvf apache-maven-3.5.4-bin.tar.gz ./

修改settings.xml文件，设置镜像加速：

$ vim apache-maven-3.5.4/conf/settings.xml

设置本地仓库：

<localRepository>/var/jenkins_home/repository</localRepository>

设置阿里云镜像：

	 <mirror>
          <id>nexus-aliyun</id>
          <mirrorOf>central</mirrorOf>
          <name>Nexus aliyun</name>
          <url>http://maven.aliyun.com/nexus/content/groups/public</url> 
      </mirror>

声明jdk环境：

	<profile>    
		<id>jdk-1.8</id>    
		<activation>    
			<activeByDefault>true</activeByDefault>    
			<jdk>1.8</jdk>    
		</activation>    
		<properties>    
			<maven.compiler.source>1.8</maven.compiler.source>    
			<maven.compiler.target>1.8</maven.compiler.target>    
			<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>    
		</properties>    
	</profile>

总文件：

<?xml version="1.0" encoding="UTF-8"?>

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user,
 |                 and is normally provided in ${user.home}/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.conf}/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ${user.home}/.m2/repository
  
  -->
  <localRepository>/var/jenkins_home/repository</localRepository>

  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.
   | This will have an effect on artifact downloads, artifact deployment, and others.
   |
   | Default: false
  <offline>false</offline>
  -->

  <!-- pluginGroups
   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
   |-->
  <pluginGroups>
    <!-- pluginGroup
     | Specifies a further group identifier to use for plugin lookup.
    <pluginGroup>com.your.plugins</pluginGroup>
    -->
  </pluginGroups>

  <!-- proxies
   | This is a list of proxies which can be used on this machine to connect to the network.
   | Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.
   |-->
  <proxies>
    <!-- proxy
     | Specification for one proxy, to be used in connecting to the network.
     |
    <proxy>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>proxyuser</username>
      <password>proxypass</password>
      <host>proxy.host.net</host>
      <port>80</port>
      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
    </proxy>
    -->
  </proxies>

  <!-- servers
   | This is a list of authentication profiles, keyed by the server-id used within the system.
   | Authentication profiles can be used whenever maven must make a connection to a remote server.
   |-->
  <servers>
    <!-- server
     | Specifies the authentication information to use when connecting to a particular server, identified by
     | a unique name within the system (referred to by the 'id' attribute below).
     |
     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
     |       used together.
     |
    <server>
      <id>deploymentRepo</id>
      <username>repouser</username>
      <password>repopwd</password>
    </server>
    -->

    <!-- Another sample, using keys to authenticate.
    <server>
      <id>siteServer</id>
      <privateKey>/path/to/private/key</privateKey>
      <passphrase>optional; leave empty if not used.</passphrase>
    </server>
    -->
  </servers>

  <!-- mirrors
   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
   |
   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
   | However, this repository may have problems with heavy traffic at times, so people have mirrored
   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that
   | repository, to be used as an alternate download site. The mirror site will be the preferred
   | server for that repository.
   |-->
  <mirrors>
    <!-- mirror
     | Specifies a repository mirror site to use instead of a given repository. The repository that
     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
     |
    <mirror>
      <id>mirrorId</id>
      <mirrorOf>repositoryId</mirrorOf>
      <name>Human Readable Name for this Mirror.</name>
      <url>http://my.repository.com/repo/path</url>
    </mirror>
     -->
	 <mirror>
          <id>nexus-aliyun</id>
          <mirrorOf>central</mirrorOf>
          <name>Nexus aliyun</name>
          <url>http://maven.aliyun.com/nexus/content/groups/public</url> 
      </mirror>
  </mirrors>

  <!-- profiles
   | This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
   | specific paths and repository locations which allow the build to work in the local environment.
   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a system property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |
   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
   |       repositories, plugin repositories, and free-form properties to be used as configuration
   |       variables for plugins in the POM.
   |
   |-->
  <profiles>
	<profile>    
		<id>jdk-1.8</id>    
		<activation>    
			<activeByDefault>true</activeByDefault>    
			<jdk>1.8</jdk>    
		</activation>    
		<properties>    
			<maven.compiler.source>1.8</maven.compiler.source>    
			<maven.compiler.target>1.8</maven.compiler.target>    
			<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>    
		</properties>    
	</profile> 
    <!-- profile
     | Specifies a set of introductions to the build process, to be activated using one or more of the
     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
     | or the command line, profiles have to have an ID that is unique.
     |
     | An encouraged best practice for profile identification is to use a consistent naming convention
     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
     | This will make it more intuitive to understand what the set of introduced profiles is attempting
     | to accomplish, particularly when you only have a list of profile id's for debug.
     |
     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
    <profile>
      <id>jdk-1.4</id>

      <activation>
        <jdk>1.4</jdk>
      </activation>

      <repositories>
        <repository>
          <id>jdk14</id>
          <name>Repository for JDK 1.4 builds</name>
          <url>http://www.myhost.com/maven/jdk14</url>
          <layout>default</layout>
          <snapshotPolicy>always</snapshotPolicy>
        </repository>
      </repositories>
    </profile>
    -->

    <!--
     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
     | might hypothetically look like:
     |
     | ...
     | <plugin>
     |   <groupId>org.myco.myplugins</groupId>
     |   <artifactId>myplugin</artifactId>
     |
     |   <configuration>
     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
     |   </configuration>
     | </plugin>
     | ...
     |
     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
     |       anything, you could just leave off the <value/> inside the activation-property.
     |
    <profile>
      <id>env-dev</id>

      <activation>
        <property>
          <name>target-env</name>
          <value>dev</value>
        </property>
      </activation>

      <properties>
        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
      </properties>
    </profile>
    -->
  </profiles>

  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

编辑环境变量：

$ vim /etc/profile

添加：

MAVEN_HOME=/root/download/apache-maven-3.5.4
export MAVEN_HOME
export PATH=${PATH}:${MAVEN_HOME}/bin

使配置文件生效：

$ source /etc/profile

查看maven版本：

$ mvn -version

四、jenkins界面配置

Manage Jenkins -> Global Tool Configuration，配置maven的settings.xml路径：

配置maven，点击apply应用，再save保存：

五、代码静态检查

静态检查包含findbugs、checkstyle、PMD。

• findbugs
  检测代码静态错误的插件 例如：定义了没有用到的对象，string类型的比较使用== ，NullPoint空指针检查、没有合理关闭资源、……

• checkstyle
  检测代码格式是否规范，命名规范，重复变量，是否有多余的空行，代码注释是否规范……

• PMD
  和findbugs类似,主要包括：空try/catch/finally/switch语句块未使用的局部变量、参数和private方法，空if/while语句，过于复杂的表达式，如不必要的if语句等，复杂类

六、SpringBoot项目代码静态检查

pom文件引入插件，注意reporting是project的子属性。

<reporting>
        <plugins>
            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>findbugs-maven-plugin</artifactId>
                <version>3.0.1</version>
                <configuration>
                    <xmlOutput>true</xmlOutput>
                    <!-- Optional directoryto put findbugs xdoc xml report -->
                    <!-- <xmlOutputDirectory>target/site</xmlOutputDirectory>-->
                    <findbugsXmlOutput>true</findbugsXmlOutput>
                    <findbugsXmlWithMessages>true</findbugsXmlWithMessages>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-pmd-plugin</artifactId>
                <version>3.8</version>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-checkstyle-plugin</artifactId>
                <version>2.17</version>
                <reportSets>
                    <reportSet>
                        <reports>
                            <report>checkstyle</report>
                        </reports>
                    </reportSet>
                </reportSets>
            </plugin>
        </plugins>
    </reporting>

jenkins主界面点击New Item，输入项目名称，选择Maven Project创建新项目：

选择版本管理工具，输入资源库地址以及用户信息，分支。

构建时执行maven命令进行代码静态检查：

-Dmaven.test.skip=true  findbugs:findbugs checkstyle:checkstyle pmd:pmd site

点击apply->save。
点击Build Now，立即构建:

构建成功后查看检查信息：

七、docker镜像

安装docker插件 docker-build-step：


系统配置：
ManageJenkins->Configure System，找到Docker Builder，并配置tcp路径：tcp://192.168.0.150:2375

• 192.168.0.150为docker主机ip
• 2375为docker开放的端口， 配置可见《docker部署之私服管理》第四节
  
  配置docker步骤：

1. 使用dockerfile构建镜像：
   
2. 推送到私服镜像仓库
   
3. 执行shell命令：
   

#!/bin/bash
IMAGE_NAME=192.168.0.150:9000/pension/jeeplus
SERVER_NAME=pension
JENKINS_HOME=/var/jenkins_home
PENSION_HOME=$JENKINS_HOME/workspace/$SERVER_NAME
cd $PENSION_HOME
docker-compose down
echo "停止并删除容器"
rm -rf $PENSION_HOME/docker-compose.yml
touch $PENSION_HOME/docker-compose.yml
cat >>$PENSION_HOME/docker-compose.yml<<EOF
version: '3'
services:
    $SERVER_NAME:
        container_name: $SERVER_NAME
        hostname: 192.168.0.150
        image: $IMAGE_NAME:v$BUILD_NUMBER
        restart: always 
        privileged: true
        environment:
           TZ: 'Asia/Shanghai'
        volumes:
          - "/usr/jeeplus/userfiles:/jeeplus/userfiles"
        ports:
          - "8082:8082"
EOF
docker-compose up -d
echo "容器启动完成"

 此段代码作为在于利用docker-compose down停止之前的服务，再重新编写docker-compose.yml，再利用docker-compose up启动服务。
 如果执行此段命令时遇到docker command not found，是因为jenkins中不能执行docker命令，解决办法请参考《解决Jenkins中的docker in docker问题》。