11 基于 Docker 构建 Jenkins CI 平台

11.1 CI/CD概述

持续集成(Continuous Integration，Cl)：代码合并、构建、部署、测试都在一起，不断地执行这个过程，并对结果反馈。

持续部署(Continuous Deployment，CD)：部署到测试环境、预生产环境、生产环境。

持续交付(Continuous Delivery，CD)：将最终产品发布到生产环境，给用户使用。

03 Docker CICD 部分 - 图1

11.2 CI工作流程设计

03 Docker CICD 部分 - 图2

CI 工作流程

拓展：

Git 代码版本管理系统

GitLab 基于Git做图形管理页面

GitHub 公共的代码管理仓库

IP地址 主机名 角色
10.0.0.100 harbor-ssh-server Harbor 镜像仓库
10.0.0.101 jenkins-ssh-server Jenkins CICD
10.0.0.102 gitlab-ssh-server GitLab 代码仓库

11.3 部署 GitLab

11.3.1 部署 GitLab

  1. mkdir gitlab && cd gitlab
  2. docker run -d \
  3. --name gitlab \
  4. -p 8443:443 \
  5. -p 9999:80 \
  6. -p 9998:22 \
  7. -v $PWD/config:/etc/gitlab \
  8. -v $PWD/logs:/var/log/gitlab \
  9. -v $PWD/data:/var/opt/gitlab \
  10. -v /etc/localtime:/etc/localtime \
  11. --restart=always \
  12. lizhenliang/gitlab-ce-zh:latest
  14. # 查看GitLab的容器日志
  15. $ docker logs -f gitlab

访问地址:：http://<IP地址>:9999

03 Docker CICD 部分 - 图3

初次会先设置管理员密码，然后登陆，默认管理员用户名root，密码就是刚设置的。

03 Docker CICD 部分 - 图4

11.3.2 创建项目，提交测试代码

进入后先创建项目，提交代码，以便后面测试。

项目名称自定义：java-devops-demo

03 Docker CICD 部分 - 图5

devops-java-demo.zip

  1. unzip devops-java-demo.zip
  2. cd devops-java-demo
  3. git init
  4. # 若无法正常推送到远程仓库，则将项目代码中的隐藏目录 .git 删除即可
  5. git remote add origin http://10.0.0.102:9999/root/java-devops-demo.git
  6. git add .
  7. # git config --global user.email "Your@example.com"
  8. # git config --global user.name "Your Name"
  9. git config --global user.email "zhongzhiwei@kubesphere.io"
  10. git config --global user.name "zhongzhiwei"
  11. git commit -m "all"
  13. $ git push origin master 
  14. Username for 'http://10.0.0.102:9999': root
  15. Password for 'http://root@10.0.0.102:9999': [Gitlab root密码]
  • GitLab 代码仓库中就有相应的代码

使用 https://github.com/Dragon-zw/tomcat-java-demo.git 代码

  1. unzip devops-java-demo.zip
  2. cd devops-java-demo
  3. git init
  4. # 若无法正常推送到远程仓库，则将项目代码中的隐藏目录 .git 删除即可
  5. git remote add origin http://10.0.0.102:9999/root/java-devops-demo.git
  6. git add .
  7. # git config --global user.email "Your@example.com"
  8. # git config --global user.name "Your Name"
  9. git config --global user.email "zhongzhiwei@kubesphere.io"
  10. git config --global user.name "zhongzhiwei"
  11. git commit -m "all"
  13. $ git push origin master 
  14. Username for 'http://10.0.0.102:9999': root
  15. Password for 'http://root@10.0.0.102:9999': [Gitlab root密码]

03 Docker CICD 部分 - 图6

GitLab 代码项目仓库中就拥有该代码

03 Docker CICD 部分 - 图7

11.4 部署 Harbor 镜像仓库

11.4.1 安装 Docker 和 Docker-Compose

范例：Ubuntu 20.04 部署 Docker 和 Docker-Compose 脚本

  1. #!/bin/bash
  2. #Description: ubuntu20.04系统安装docker-compose编排工具
  4. COLOR="echo -e \\033[1;31m"
  5. END="\033[m"
  6. DOCKER_VERSION="5:20.10.21~3-0~ubuntu-focal"
  8. install_docker(){
  9. ${COLOR}"开始安装 Docker....."${END}
  10. sleep 1 
  12. apt update
  13. apt  -y install apt-transport-https ca-certificates curl software-properties-common 
  14. curl -fsSL https://mirrors.aliyun.com/docker-ce/linux/ubuntu/gpg | sudo apt-key add -
  15. add-apt-repository "deb [arch=amd64] https://mirrors.aliyun.com/docker-ce/linux/ubuntu $(lsb_release -cs) stable"
  16. apt update
  18. ${COLOR}"Docker有以下版本:"${END}
  19. sleep 2
  20. apt-cache madison docker-ce
  21. ${COLOR}"5秒后即将安装: docker-"${DOCKER_VERSION}" 版本....."${END}
  22. ${COLOR}"如果想安装其它Docker版本，请按ctrl+c键退出，修改版本再执行"${END}
  23. sleep 5
  25. apt -y  install docker-ce=${DOCKER_VERSION} docker-ce-cli=${DOCKER_VERSION}
  27. mkdir -p /etc/docker
  28. tee /etc/docker/daemon.json <<-'EOF'
  29. {
  30.   "registry-mirrors": ["https://po13h3y1.mirror.aliyuncs.com","http://hub-mirror.c.163.com","https://mirror.ccs.tencentyun.com","http://f1361db2.m.daocloud.io"],
  31.   "exec-opts": ["native.cgroupdriver=systemd"],
  32.   "log-driver": "json-file",
  33.   "log-opts": {
  34.     "max-size": "100m"
  35.   },
  36.   "storage-driver": "overlay2"
  37. }
  38. EOF
  39. systemctl daemon-reload
  40. systemctl restart docker
  41. docker version && ${COLOR}"Docker 安装完成"${END} ||  ${COLOR}"Docker 安装失败"${END}
  42. }
  44. install_docker_compose(){
  45. ${COLOR}"开始安装 Docker compose....."${END}
  46. sleep 1
  48. # curl -L https://github.com/docker/compose/releases/download/1.25.3/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
  49. # chmod +x /usr/local/bin/docker-compose
  50. curl -L https://get.daocloud.io/docker/compose/releases/download/v2.13.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
  51. chmod +x /usr/local/bin/docker-compose
  53. docker-compose --version &&  ${COLOR}"Docker Compose 安装完成"${END} ||  ${COLOR}"Docker compose 安装失败"${END}
  54. }
  56. dpkg -s docker-ce &> /dev/null && ${COLOR}"Docker已安装"${END} || install_docker
  58. docker-compose --version &> /dev/null && ${COLOR}"Docker Compose已安装"${END} || install_docker_compose

范例：CentOS & Ubuntu 全系列部署 Docker 和 Docker-Compose 脚本

  1. #!/bin/bash
  2. #Description：全系列系统安装 docker harbor镜像仓库
  4. DOCKER_VERSION="20.10.10"
  5. #DOCKER_VERSION="19.03.14"
  7. DOCKER_COMPOSE_VERSION=2.6.1
  8. #DOCKER_COMPOSE_VERSION=1.29.2
  9. DOCKER_COMPOSE_FILE=docker-compose-Linux-x86_64
  11. #HARBOR_NAME=`hostname -I|awk '{print $1}'`
  12. HARBOR_ADMIN_PASSWORD=123456
  14. HARBOR_IP=`hostname -I|awk '{print $1}'`
  16. COLOR_SUCCESS="echo -e \\033[1;32m"
  17. COLOR_FAILURE="echo -e \\033[1;31m"
  18. END="\033[m"
  20. . /etc/os-release
  21. UBUNTU_DOCKER_VERSION="5:${DOCKER_VERSION}~3-0~${ID}-${UBUNTU_CODENAME}"
  23. color () {
  24.     RES_COL=60
  25.     MOVE_TO_COL="echo -en \\033[${RES_COL}G"
  26.     SETCOLOR_SUCCESS="echo -en \\033[1;32m"
  27.     SETCOLOR_FAILURE="echo -en \\033[1;31m"
  28.     SETCOLOR_WARNING="echo -en \\033[1;33m"
  29.     SETCOLOR_NORMAL="echo -en \E[0m"
  30.     echo -n "$1" && $MOVE_TO_COL
  31.     echo -n "["
  32.     if [ $2 = "success" -o $2 = "0" ] ;then
  33.         ${SETCOLOR_SUCCESS}
  34.         echo -n $"  OK  "    
  35.     elif [ $2 = "failure" -o $2 = "1"  ] ;then 
  36.         ${SETCOLOR_FAILURE}
  37.         echo -n $"FAILED"
  38.     else
  39.         ${SETCOLOR_WARNING}
  40.         echo -n $"WARNING"
  41.     fi
  42.     ${SETCOLOR_NORMAL}
  43.     echo -n "]"
  44.     echo 
  45. }
  47. install_docker(){
  48.     if [ $ID = "centos" -o $ID = "rocky" ];then
  49.         if [ $VERSION_ID = "7" ];then
  50.             cat >  /etc/yum.repos.d/docker.repo  <<EOF
  51. [docker]
  52. name=docker
  53. gpgcheck=0
  54. #baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/x86_64/stable/
  55. baseurl=https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/centos/7/x86_64/stable/
  56. EOF
  57.         else     
  58.             cat >  /etc/yum.repos.d/docker.repo  <<EOF
  59. [docker]
  60. name=docker
  61. gpgcheck=0
  62. #baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/8/x86_64/stable/
  63. baseurl=https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/centos/8/x86_64/stable/
  64. EOF
  65.         fi
  66.         yum clean all 
  67.         ${COLOR_FAILURE} "Docker有以下版本"${END}
  68.         yum list docker-ce --showduplicates
  69.         ${COLOR_FAILURE}"5秒后即将安装: docker-"${DOCKER_VERSION}" 版本....."${END}
  70.         ${COLOR_FAILURE}"如果想安装其它Docker版本，请按ctrl+c键退出，修改版本再执行"${END}
  71.         sleep 5
  72.         yum -y install docker-ce-$DOCKER_VERSION docker-ce-cli-$DOCKER_VERSION  \
  73.             || { color "Base,Extras的yum源失败,请检查yum源配置" 1;exit; }
  74.     else
  75.         dpkg -s docker-ce &> /dev/null && $COLOR"Docker已安装，退出" 1 && exit
  76.         apt update || { color "更新包索引失败" 1 ; exit 1; }  
  77.         apt  -y install apt-transport-https ca-certificates curl software-properties-common || \
  78.             { color "安装相关包失败" 1 ; exit 2;  }  
  79.         curl -fsSL https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/ubuntu/gpg | sudo apt-key add -
  80.         add-apt-repository "deb [arch=amd64] https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/ubuntu $(lsb_release -cs) stable"
  81.         apt update
  82.         ${COLOR_FAILURE} "Docker有以下版本"${END}
  83.         apt-cache madison docker-ce
  84.         ${COLOR_FAILURE}"5秒后即将安装: docker-"${UBUNTU_DOCKER_VERSION}" 版本....."${END}
  85.         ${COLOR_FAILURE}"如果想安装其它Docker版本，请按ctrl+c键退出，修改版本再执行"${END}
  86.         sleep 5
  87.         apt -y  install docker-ce=${UBUNTU_DOCKER_VERSION} docker-ce-cli=${UBUNTU_DOCKER_VERSION}
  88.     fi
  89.     if [ $? -eq 0 ];then
  90.         color "安装软件包成功"  0
  91.     else
  92.         color "安装软件包失败，请检查网络配置" 1
  93.         exit
  94.     fi
  96.     mkdir -p /etc/docker
  97.     tee /etc/docker/daemon.json <<-'EOF'
  98. {
  99.   "registry-mirrors": ["https://po13h3y1.mirror.aliyuncs.com","http://hub-mirror.c.163.com","https://mirror.ccs.tencentyun.com","http://f1361db2.m.daocloud.io"],
  100.   "exec-opts": ["native.cgroupdriver=systemd"],
  101.   "log-driver": "json-file",
  102.   "log-opts": {
  103.     "max-size": "100m"
  104.   },
  105.   "storage-driver": "overlay2"
  106. }
  107. EOF
  108.     systemctl daemon-reload
  109.     systemctl enable docker
  110.     systemctl restart docker
  111.     docker version && color "Docker 安装成功" 0 ||  color "Docker 安装失败" 1
  112.     echo 'alias rmi="docker images -qa|xargs docker rmi -f"' >> ~/.bashrc
  113.     echo 'alias rmc="docker ps -qa|xargs docker rm -f"' >> ~/.bashrc
  114. }
  116. install_docker_compose(){
  117.     if [ $ID = "centos" -o $ID = "rocky" ];then
  118.         ${COLOR_SUCCESS}"开始安装 Docker compose....."${END}
  119.         sleep 1
  120.         if [ ! -e  ${DOCKER_COMPOSE_FILE} ];then
  121.             #curl -L https://github.com/docker/compose/releases/download/${DOCKER_COMPOSE_VERSION}/${DOCKER_COMPOSE_FILE} -o /usr/bin/docker-compose
  122.             curl -L https://get.daocloud.io/docker/compose/releases/download/v${DOCKER_COMPOSE_VERSION}/docker-compose-$(uname -s)-$(uname -m) -o /usr/bin/docker-compose
  123.         else
  124.             mv ${DOCKER_COMPOSE_FILE} /usr/bin/docker-compose
  125.         fi
  126.         chmod +x /usr/bin/docker-compose
  127.     else 
  128.         apt -y install docker-compose
  129.     fi
  130.     if docker-compose --version ;then
  131.         ${COLOR_SUCCESS}"Docker Compose 安装完成"${END} 
  132.     else
  133.         ${COLOR_FAILURE}"Docker compose 安装失败"${END}
  134.         exit
  135.     fi
  136. }
  138. docker info  &> /dev/null  && ${COLOR_FAILURE}"Docker已安装"${END} || install_docker
  140. docker-compose --version &> /dev/null && ${COLOR_FAILURE}"Docker Compose已安装"${END} || install_docker_compose

11.4.2 解压离线包部署

  1. # https://github.com/goharbor/harbor/releases/download/v2.6.2/harbor-offline-installer-v2.6.2.tgz
  2. $ tar -zxvf harbor-offline-installer-v2.6.2.tgz
  3. $ cd harbor
  5. $ cp harbor.yml.tmpl harbor.yml
  6. $ vim harbor.yml
  7. hostname: reg.kubesphere.com
  8. https:    #先注释https相关配置
  9. harbor_admin_password: Harbor12345
  11. # 部署Harbor HTTP
  12. $ ./prepare
  13. $ ./install.sh

03 Docker CICD 部分 - 图8

  1. $ docker-compose ps 
  2.       Name                     Command                       State                          Ports                
  3. -----------------------------------------------------------------------------------------------------------------
  4. harbor-core         /harbor/entrypoint.sh            Up (health: starting)                                       
  5. harbor-db           /docker-entrypoint.sh 96 13      Up (health: starting)                                       
  6. harbor-jobservice   /harbor/entrypoint.sh            Up (health: starting)                                       
  7. harbor-log          /bin/sh -c /usr/local/bin/ ...   Up (health: starting)   127.0.0.1:1514->10514/tcp           
  8. harbor-portal       nginx -g daemon off;             Up (health: starting)                                       
  9. nginx               nginx -g daemon off;             Up (health: starting)   0.0.0.0:80->8080/tcp,:::80->8080/tcp
  10. redis               redis-server /etc/redis.conf     Up (health: starting)                                       
  11. registry            /home/harbor/entrypoint.sh       Up (health: starting)                                       
  12. registryctl         /home/harbor/start.sh            Up (health: starting)

浏览器访问http://<IP地址>:80也可以修改主机的host文件将IP地址 域名进行绑定

默认用户名：admin

默认密码：Harbor12345

03 Docker CICD 部分 - 图9

Harbor 的主界面

03 Docker CICD 部分 - 图10

  1. cat >> /etc/hosts <<EOF
  3. # KubeSphere Harbor Host BEGIN
  4. 10.0.0.100 reg.kubesphere.com
  5. # KubeSphere Harbor Host END
  6. EOF

11.4.3 在 Jenkins 主机配置Docker可信任，如果是HTTPS需要拷贝证书

由于Harbor未配置https，还需要在docker配置可信任。

  1. $ cat /etc/docker/daemon.json 
  2. {
  3.   "registry-mirrors": ["https://po13h3y1.mirror.aliyuncs.com","http://hub-mirror.c.163.com","https://mirror.ccs.tencentyun.com","http://f1361db2.m.daocloud.io"],
  4.   "exec-opts": ["native.cgroupdriver=systemd"],
  5.   "log-driver": "json-file",
  6.   "log-opts": {
  7.     "max-size": "100m"
  8.   },
  9.   "storage-driver": "overlay2",
  10.   "insecure-registries": ["reg.kubesphere.com"]
  11. }

11.5 部署 Jenkins

11.5.1 准备JDK 和 Maven 环境

将二进制包上传到服务器并解压到工作目录，用于让Jenkins容器挂载使用。

  1. # JDK Download:https://lupf.cn/articles/2022/02/19/1645283667689.html
  2. # Maven Download:https://dlcdn.apache.org/maven/maven-3/3.5.4/binaries/
  3. # wget https://dlcdn.apache.org/maven/maven-3/3.5.4/binaries/apache-maven-3.5.4-bin.tar.gz --no-check-certificate
  4. tar -zxvf jdk-8u45-linux-x64.tar.gz
  5. mv jdk1.8.0_45/ /usr/local/jdk
  6. tar -zxvf apache-maven-3.5.4-bin.tar.gz
  7. mv apache-maven-3.5.4/ /usr/local/maven

修改Maven源：

  1. # docker pull jenkins/jenkins:lts
  2. docker pull jenkins/jenkins:2.375.1-lts
  4. docker run -d --name jenkins -p 80:8080 -p 50000:50000 -u root \
  5. -v /opt/jenkins_home:/var/jenkins_home \
  6. -v /var/run/docker.sock:/var/run/docker.sock \
  7. -v /usr/bin/docker:/usr/bin/docker \
  8. -v /usr/local/maven:/usr/local/maven \
  9. -v /usr/local/jdk:/usr/local/jdk \
  10. -v /etc/localtime:/etc/localtime \
  11. --restart=always \
  12. --name jenkins jenkins/jenkins:2.375.1-lts
  14. # 查看Jenkins日志
  15. $ docker logs -f jenkins

访问地址：http://IP

03 Docker CICD 部分 - 图11

:::warning Jenkins 是类似于 Docker in Docker 的模式

:::

  1. # 获取Jenkins的管理员密码
  2. $ docker exec -it jenkins cat /var/jenkins_home/secrets/initialAdminPassword
  3. 2f9c8ca73c98418182bd1af7a19a37ca

Jenkins 使用安装推荐的插件

03 Docker CICD 部分 - 图12

11.5.2 安装插件

管理Jenkins→系统配置→管理插件→搜索git/pipeline/blue ocean，选中点击安装。默认从国外网络下载插件，会比较慢，建议修改国内源：

  1. $ docker exec -it jenkins /bin/bash
  2. cd /opt/jenkins_home/updates
  3. # sed -i 's/https:\/\/updates.jenkins.io\/download/http:\/\/mirrors.tuna.tsinghua.edu.cn\/jenkins/g' /var/lib/jenkins/updates/default.json
  4. # sed -i 's/https:\/\/www.google.com/https:\/\/www.baidu.com/g' /var/lib/jenkins/updates/default.json
  5. sed -i 's/https:\/\/updates.jenkins.io\/download/http:\/\/mirrors.tuna.tsinghua.edu.cn\/jenkins/g' /opt/jenkins_home/updates/default.json
  6. sed -i 's/https:\/\/www.google.com/https:\/\/www.baidu.com/g' /opt/jenkins_home/updates/default.json
  8. $ docker restart jenkins

11.6 发布测试

11.6.1 创建项目并配置

New ltem → Pipeline → This project is parameterized → String Parameter

  • Name: Branch #变量名，下面脚本中调用
  • Default Value: master #默认分支
  • Description: 发布的代码分支 #描述

03 Docker CICD 部分 - 图13

11.6.2 Pipeline 脚本

初始化Pipeline 脚本范例：

  1. pipeline {
  2.     agent any
  4.     stages {
  5.         stage('1.拉取代码') {
  6.             steps {
  7.                 echo '拉取代码'
  8.             }
  9.         }
  11.         stage('2.代码编译') {
  12.             steps {
  13.                 echo '代码编译'
  14.             }
  15.         }
  17.         stage('3.部署代码') {
  18.             steps {
  19.                 echo '部署代码'
  20.             }
  21.         }
  22.     }
  23. }

03 Docker CICD 部分 - 图14

结果看板

03 Docker CICD 部分 - 图15

最终的Jenkinsfile Pipeline示例

  1. #!/usr/bin/env groovy
  3. // 定义镜像仓库地址
  4. def registry = "reg.kubesphere.com"
  5. def project = "welcome"
  6. def app_name = "demo"
  7. // 需要    Groovy Postbuild Jenkins 插件
  8. def image_name = "${registry}/${project}/${app_name}:${Branch}-${BUILD_NUMBER}"
  9. // GitLab的地址
  10. def git_address = "http://10.0.0.102:9999/root/java-devops-demo.git"
  11. // 连接Harbor的用户名和密码
  12. def docker_registry_auth = "d5c0e5c2-5a39-496e-86ae-697a448f5b84"
  13. // 连接GitLab的用户名和密码
  14. def git_auth = "6d59e843-034f-4531-8705-d7f6c1f40b23"
  16. pipeline {
  17.     agent any
  18.     stages {
  19.         stage('拉取代码') {
  20.             steps {
  21.                 checkout ([$class: 'GitSCM', branches: [[name: "${Branch}"]], userRemoteConfigs: [[credentialsId: "${git_auth}", url: "${git_address}"]]])
  22.             }
  23.         }
  24.         stage('代码编译') {
  25.             steps {
  26.                 sh """
  27.                     pwd
  28.                     JAVA_HOME=/usr/local/jdk
  29.                     PATH=$JAVA_HOME/bin:/usr/local/maven/bin:$PATH
  30.                     java -version
  31.                     mvn clean package -Dmaven.test.skip=true
  32.                     ls -alhR
  33.                 """
  34.             }
  35.         }
  36.         stage('构建镜像') {
  37.             steps {
  38.                 withCredentials([usernamePassword(credentialsId: "${docker_registry_auth}",passwordVariable: "password",usernameVariable: "username")]) {
  39.                 sh """
  40.                     echo '
  41.                         FROM lizhenliang/tomcat:latest
  42.                         LABEL maintainer zhongzhiwei <zhongzhiwei@kubesphere.io>
  43.                         RUN rm -rf /usr/local/tomcat/webapps/*
  44.                         ADD target/*.war /usr/local/tomcat/webapps/ROOT.war
  45.                     ' > Dockerfile
  46.                     docker build -t ${image_name} .
  47.                     docker login -u ${username} -p '${password}' ${registry}
  48.                     docker push ${image_name}
  49.                 """
  50.                 }
  51.             }
  52.         }
  53.         stage('部署到Docker') {
  54.             steps {
  55.                 sh """
  56.                     docker rm -f tomcat-java-demo | true
  57.                     docker container run -d --name tomcat-java-demo -p 18080:8080 ${image_name}
  58.                 """
  59.             }
  60.         }
  61.     }
  62. }

使用阿里云Maven镜像加速 **/usr/local/maven/conf/settings.xml**

  1. cat settings.xml
  2. <?xml version="1.0" encoding="UTF-8"?>
  4. <!--
  5. Licensed to the Apache Software Foundation (ASF) under one
  6. or more contributor license agreements.  See the NOTICE file
  7. distributed with this work for additional information
  8. regarding copyright ownership.  The ASF licenses this file
  9. to you under the Apache License, Version 2.0 (the
  10. "License"); you may not use this file except in compliance
  11. with the License.  You may obtain a copy of the License at
  13.     http://www.apache.org/licenses/LICENSE-2.0
  15. Unless required by applicable law or agreed to in writing,
  16. software distributed under the License is distributed on an
  17. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  18. KIND, either express or implied.  See the License for the
  19. specific language governing permissions and limitations
  20. under the License.
  21. -->
  23. <!--
  24.  | This is the configuration file for Maven. It can be specified at two levels:
  25.  |
  26.  |  1. User Level. This settings.xml file provides configuration for a single user,
  27.  |                 and is normally provided in ${user.home}/.m2/settings.xml.
  28.  |
  29.  |                 NOTE: This location can be overridden with the CLI option:
  30.  |
  31.  |                 -s /path/to/user/settings.xml
  32.  |
  33.  |  2. Global Level. This settings.xml file provides configuration for all Maven
  34.  |                 users on a machine (assuming they're all using the same Maven
  35.  |                 installation). It's normally provided in
  36.  |                 ${maven.conf}/settings.xml.
  37.  |
  38.  |                 NOTE: This location can be overridden with the CLI option:
  39.  |
  40.  |                 -gs /path/to/global/settings.xml
  41.  |
  42.  | The sections in this sample file are intended to give you a running start at
  43.  | getting the most out of your Maven installation. Where appropriate, the default
  44.  | values (values used when the setting is not specified) are provided.
  45.  |
  46.  |-->
  47. <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  48.           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  49.           xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  50.   <!-- localRepository
  51.    | The path to the local repository maven will use to store artifacts.
  52.    |
  53.    | Default: ${user.home}/.m2/repository
  54.   <localRepository>/path/to/local/repo</localRepository>
  55.   -->
  57.   <!-- interactiveMode
  58.    | This will determine whether maven prompts you when it needs input. If set to false,
  59.    | maven will use a sensible default value, perhaps based on some other setting, for
  60.    | the parameter in question.
  61.    |
  62.    | Default: true
  63.   <interactiveMode>true</interactiveMode>
  64.   -->
  66.   <!-- offline
  67.    | Determines whether maven should attempt to connect to the network when executing a build.
  68.    | This will have an effect on artifact downloads, artifact deployment, and others.
  69.    |
  70.    | Default: false
  71.   <offline>false</offline>
  72.   -->
  74.   <!-- pluginGroups
  75.    | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
  76.    | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
  77.    | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
  78.    |-->
  79.   <pluginGroups>
  80.     <!-- pluginGroup
  81.      | Specifies a further group identifier to use for plugin lookup.
  82.     <pluginGroup>com.your.plugins</pluginGroup>
  83.     -->
  84.   </pluginGroups>
  86.   <!-- proxies
  87.    | This is a list of proxies which can be used on this machine to connect to the network.
  88.    | Unless otherwise specified (by system property or command-line switch), the first proxy
  89.    | specification in this list marked as active will be used.
  90.    |-->
  91.   <proxies>
  92.     <!-- proxy
  93.      | Specification for one proxy, to be used in connecting to the network.
  94.      |
  95.     <proxy>
  96.       <id>optional</id>
  97.       <active>true</active>
  98.       <protocol>http</protocol>
  99.       <username>proxyuser</username>
  100.       <password>proxypass</password>
  101.       <host>proxy.host.net</host>
  102.       <port>80</port>
  103.       <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
  104.     </proxy>
  105.     -->
  106.   </proxies>
  108.   <!-- servers
  109.    | This is a list of authentication profiles, keyed by the server-id used within the system.
  110.    | Authentication profiles can be used whenever maven must make a connection to a remote server.
  111.    |-->
  112.   <servers>
  113.     <!-- server
  114.      | Specifies the authentication information to use when connecting to a particular server, identified by
  115.      | a unique name within the system (referred to by the 'id' attribute below).
  116.      |
  117.      | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
  118.      |       used together.
  119.      |
  120.     <server>
  121.       <id>deploymentRepo</id>
  122.       <username>repouser</username>
  123.       <password>repopwd</password>
  124.     </server>
  125.     -->
  127.     <!-- Another sample, using keys to authenticate.
  128.     <server>
  129.       <id>siteServer</id>
  130.       <privateKey>/path/to/private/key</privateKey>
  131.       <passphrase>optional; leave empty if not used.</passphrase>
  132.     </server>
  133.     -->
  134.   </servers>
  136.   <!-- mirrors
  137.    | This is a list of mirrors to be used in downloading artifacts from remote repositories.
  138.    |
  139.    | It works like this: a POM may declare a repository to use in resolving certain artifacts.
  140.    | However, this repository may have problems with heavy traffic at times, so people have mirrored
  141.    | it to several places.
  142.    |
  143.    | That repository definition will have a unique id, so we can create a mirror reference for that
  144.    | repository, to be used as an alternate download site. The mirror site will be the preferred
  145.    | server for that repository.
  146.    |-->
  147.   <mirrors>
  148.     <!-- mirror
  149.      | Specifies a repository mirror site to use instead of a given repository. The repository that
  150.      | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
  151.      | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
  152.      |
  153.     <mirror>
  154.       <id>mirrorId</id>
  155.       <mirrorOf>repositoryId</mirrorOf>
  156.       <name>Human Readable Name for this Mirror.</name>
  157.       <url>http://my.repository.com/repo/path</url>
  158.     </mirror>
  159.      -->
  160.     <!--     
  161.     <mirror>
  162.       <id>nexus</id>
  163.       <mirrorOf>*</mirrorOf>
  164.       <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
  165.     </mirror>
  166.     <mirror>
  167.       <id>nexus-public-snapshots</id>
  168.       <mirrorOf>public-snapshots</mirrorOf>
  169.       <url>http://maven.aliyun.com/nexus/content/repositories/snapshots/</url>
  170.     </mirror>
  171.     <mirror>
  172.       <id>nexus-public-snapshots1</id>
  173.       <mirrorOf>public-snapshots1</mirrorOf>
  174.       <url>https://artifacts.alfresco.com/nexus/content/repositories/public/</url>
  175.     </mirror> 
  176.     -->
  177.     <mirror>
  178.       <id>central</id>
  179.       <mirrorOf>central</mirrorOf>
  180.       <name>aliyun maven</name>
  181.       <url>https://maven.aliyun.com/repository/public</url>
  182.     </mirror>
  183.   </mirrors>
  185.   <!-- profiles
  186.    | This is a list of profiles which can be activated in a variety of ways, and which can modify
  187.    | the build process. Profiles provided in the settings.xml are intended to provide local machine-
  188.    | specific paths and repository locations which allow the build to work in the local environment.
  189.    |
  190.    | For example, if you have an integration testing plugin - like cactus - that needs to know where
  191.    | your Tomcat instance is installed, you can provide a variable here such that the variable is
  192.    | dereferenced during the build process to configure the cactus plugin.
  193.    |
  194.    | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
  195.    | section of this document (settings.xml) - will be discussed later. Another way essentially
  196.    | relies on the detection of a system property, either matching a particular value for the property,
  197.    | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
  198.    | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
  199.    | Finally, the list of active profiles can be specified directly from the command line.
  200.    |
  201.    | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
  202.    |       repositories, plugin repositories, and free-form properties to be used as configuration
  203.    |       variables for plugins in the POM.
  204.    |
  205.    |-->
  206.   <profiles>
  207.     <!-- profile
  208.      | Specifies a set of introductions to the build process, to be activated using one or more of the
  209.      | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
  210.      | or the command line, profiles have to have an ID that is unique.
  211.      |
  212.      | An encouraged best practice for profile identification is to use a consistent naming convention
  213.      | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
  214.      | This will make it more intuitive to understand what the set of introduced profiles is attempting
  215.      | to accomplish, particularly when you only have a list of profile id's for debug.
  216.      |
  217.      | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
  218.     <profile>
  219.       <id>jdk-1.4</id>
  221.       <activation>
  222.         <jdk>1.4</jdk>
  223.       </activation>
  225.       <repositories>
  226.         <repository>
  227.           <id>jdk14</id>
  228.           <name>Repository for JDK 1.4 builds</name>
  229.           <url>http://www.myhost.com/maven/jdk14</url>
  230.           <layout>default</layout>
  231.           <snapshotPolicy>always</snapshotPolicy>
  232.         </repository>
  233.       </repositories>
  234.     </profile>
  235.     -->
  237.     <!--
  238.      | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
  239.      | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
  240.      | might hypothetically look like:
  241.      |
  242.      | ...
  243.      | <plugin>
  244.      |   <groupId>org.myco.myplugins</groupId>
  245.      |   <artifactId>myplugin</artifactId>
  246.      |
  247.      |   <configuration>
  248.      |     <tomcatLocation>${tomcatPath}</tomcatLocation>
  249.      |   </configuration>
  250.      | </plugin>
  251.      | ...
  252.      |
  253.      | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
  254.      |       anything, you could just leave off the <value/> inside the activation-property.
  255.      |
  256.     <profile>
  257.       <id>env-dev</id>
  259.       <activation>
  260.         <property>
  261.           <name>target-env</name>
  262.           <value>dev</value>
  263.         </property>
  264.       </activation>
  266.       <properties>
  267.         <tomcatPath>/path/to/tomcat/instance</tomcatPath>
  268.       </properties>
  269.     </profile>
  270.     -->
  271.   </profiles>
  273.   <!-- activeProfiles
  274.    | List of profiles that are active for all builds.
  275.    |
  276.   <activeProfiles>
  277.     <activeProfile>alwaysActiveProfile</activeProfile>
  278.     <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  279.   </activeProfiles>
  280.   -->
  281. </settings>

11.6.3 添加凭证

  • 添加字符参数

03 Docker CICD 部分 - 图16

  • 添加 Harbor 私有镜像的凭证( 需要确保凭证的信息正确 )

03 Docker CICD 部分 - 图17

  • 添加 GitLab 私有代码仓库的凭证( 需要确保凭证的信息正确 )

03 Docker CICD 部分 - 图18

  • 使用 Jenkins 生成的ID号。

03 Docker CICD 部分 - 图19

11.6.4 运行构建

  • Jenkins 查看流水线的状态

03 Docker CICD 部分 - 图20

03 Docker CICD 部分 - 图21

  • Harbor 镜像仓库的镜像上传状态

03 Docker CICD 部分 - 图22

  • 访问部署页面

03 Docker CICD 部分 - 图23

11.7 Jenkins Pipeline

Jenkins Pipeline是一套插件，支持在Jenkins中实现集成和持续交付管道；

Pipeline通过特定语法对简单到复杂的传输管道进行建模;

  • 声明式：遵循与<font style="color:#E8323C;">Groovy</font>相同语法。<font style="color:#E8323C;">pipeline { }</font>
  • 脚本式：支持Groovy大部分功能，也是非常表达和灵活的工具。node { }

Jenkins Pipeline的定义被写入一个文本文件，称为Jenkinsfile。

  1. Jenkinsfile (Declarative Pipeline)
  2. pipeline {
  3.     agent any 
  4.     stages {
  5.         stage('Build') { 
  6.             steps {
  7.                 // 
  8.             }
  9.         }
  10.         stage('Test') { 
  11.             steps {
  12.                 // 
  13.             }
  14.         }
  15.         stage('Deploy') { 
  16.             steps {
  17.                 // 
  18.             }
  19.         }
  20.     }
  21. }

03 Docker CICD 部分 - 图24

:::warning

  1. 在任何可用的代理上，执行流水线或它的任何阶段。
  2. 定义“Build”阶段。
  3. 执行与”Build”阶段相关的步骤。
  4. 定义”Test”阶段。
  5. 执行与”Test”阶段相关的步骤。
  6. 定义“Deploy”阶段。
  7. 执行与”Deploy”阶段相关的步骤。

:::

03 Docker CICD 部分 - 图25

11.8 CI/CD收益

高效的CI/CD环境可以获得：

  • 及时发现问题
  • 大幅度减少故障率
  • 加快迭代速度
  • 减少时间成本