maven + git + gitlab-runner实现远程服务的自动打包发布

1、远程服务器的自动打包发布

一、前提条件

git、git-runner

二、注册gitlab-runner

注册的url及token来源于git设置里CI/CD模块，如下：

执行器可以选择shell跟docker，这里我选择的是docker，默认镜像alpine:latest，注册完成之后，查看注册的gitlab-runner：

 三、编写gitlab-ci文件

stages:
  - Build

variables:
  MAVEN_CLI_OPTS: "-s .mvn/wrapper/settings.xml --batch-mode"
  MAVEN_OPTS: "-Dmaven.repo.local=.m2/repository"

cache:
  key: maven-repository-cache
  paths:
    - .m2/repository/

build:package:
  image: xxxx:xxxx/ls1/maven:3.6.1-jdk-8-alpine
  variables:
      BUILD_HOME: xxxxx
      LOCAL_HOME: xxxxx
  stage: Build
  before_script:
    - 'command -v ssh-agent >/dev/null || ( apk update -y && apk add --upgrade openssh-client -y )'
    - eval $(ssh-agent -s)
    - echo "$SSH_PRIVATE_KEY" | tr -d '\r' | ssh-add -
    - mkdir -p ~/.ssh
    - chmod 700 ~/.ssh
    - ssh-keyscan -p {服务器端口} -H {远程服务器地址} >> ~/.ssh/known_hosts
    - chmod 644 ~/.ssh/known_hosts
  script:
    - mvn $MAVEN_CLI_OPTS clean package -Dgit.revision=$CI_COMMIT_SHA -Dbuild.environment=$CI_COMMIT_REF_NAME -Dbuild.number=$CI_PIPELINE_ID
    - cd $BUILD_HOME
    - scp -P {服务器端口} xxxxx.jar {用户名}@{远程服务器地址}:{上传包路径}
    - cd $LOCAL_HOME
    - scp -P {服务器端口} xxx.jar {用户名}@{远程服务器地址}:{上传包路径}
    # 执行远程服务器脚本
    - ssh -p {服务器端口} {用户名}@{远程服务器地址} "{启动脚本路径}"
  only:
    - develop
  tags:
    - ci-test

 其中before_script部分是设置服务器的免密登录，远程复制scp这一部分，我这边是将主包跟依赖包上传到服务器，大家可以根据自己的需要调整。

2、docker+k8s的自动打包发布

一、注册gitlab-runner同上面步骤；

二、编写gitlab-ci文件

stages:
  - Build
#  - Sonarqube
  - Package
  - Deployment

variables:
  MAVEN_CLI_OPTS: "-s .mvn/wrapper/settings.xml --batch-mode"
  MAVEN_OPTS: "-Dmaven.repo.local=.m2/repository"

build:package:
  image: {远程镜像仓库地址}:3.6.1-jdk-8-alpine
  stage: Build
  script:
    - mvn $MAVEN_CLI_OPTS clean package -Dgit.revision=$CI_COMMIT_SHA -Dbuild.environment=$CI_COMMIT_REF_NAME -Dbuild.number=$CI_PIPELINE_ID
  cache:
    key: maven-repository-cache
    paths:
      - .m2/repository/
  artifacts:
    untracked: false
    expire_in: 20 mins
    paths:
      - {需要传递的内容路径}
  only:
    refs:
      - develop
      - release
      - master
  tags:
    - cj-test

#sonarqube:check:
#  image: {远程镜像仓库地址}:3.6.1-jdk-8-alpine
#  stage: Sonarqube
#  script:
#    - mvn $MAVEN_CLI_OPTS verify sonar:sonar -Dsonar.host.url=$SONAR_URL -Dsonar.login=$SONAR_TOKEN -Dsonar.projectKey=${CI_PROJECT_NAME}:${CI_COMMIT_REF_NAME} -Dsonar.projectName=${CI_PROJECT_NAME}:${CI_COMMIT_REF_NAME} -Dsonar.report.export.path=.
#  cache:
#    key: maven-repository-cache
#    paths:
#      - .m2/repository/
#  only:
#    refs:
#      - develop
#  tags:
#    - cj-test

build_docker_image:
  image:
    name: {远程镜像仓库地址}:executor-debug
    entrypoint: [""]
  stage: Package
  dependencies:
    - build:package
  variables:
    IMAGE_NAME: "{远程镜像仓库地址}:{镜像名称}"
  script:
    - echo $IMAGE_NAME
    - echo "Use kaniko for docker image build start..."
    - echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
    - /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --destination $IMAGE_NAME
    - echo "Use kaniko for docker image build end..."
  only:
    refs:
      - develop
      - release
  tags:
    - cj-test

deploytok8s:
  image: {远程镜像仓库地址}:alpine
  stage: Deployment
  script:
    - sed -i "s/__ENVIRONMENT__/${CI_COMMIT_REF_SLUG}/g" ./kube.yaml
    - sed -i "s/__VERSION__/${CI_COMMIT_REF_SLUG}-${CI_PIPELINE_ID}/g" ./kube.yaml
    - kubectl apply -f ./kube.yaml --kubeconfig "$KUBE_CONFIG"
  environment:
    name: develop
  only:
    refs:
      - develop
  tags:
    - cj-test

kube.yaml及kube_config根据每个人的k8s平台生成，Dockerfile文件也是根据项目打包镜像需要来写的，这里就不详细说明了。

另外，一些全局的参数都是设置在git里面的Variables参数里。