← 返回首页 📚 实战课程
📑 本篇章节导航 (共5章,点击直达)
本节目标(学完能回答的面试题)核心知识(1小时精讲内容)面试速记卡(考前30秒速看)练习题(自测)学习资料

L39 - CI/CD流水线

本节目标(学完能回答的面试题)

核心知识(1小时精讲内容)

1. Jenkins Pipeline(Declarative语法)


// Jenkinsfile — Declarative Pipeline
pipeline {
    agent any
    
    // 环境变量
    environment {
        DOCKER_REGISTRY = 'harbor.company.com'
        IMAGE_NAME      = 'app/order-service'
        VERSION         = "${env.BUILD_NUMBER}"
        GIT_COMMIT_SHORT = sh(script: 'git rev-parse --short HEAD', 
                              returnStdout: true).trim()
    }
    
    // 构建触发器
    triggers {
        // GitLab webhook触发
        gitlab(triggerOnPush: true, triggerOnMergeRequest: true)
        // 定时构建(可选)
        cron('H 2 * * *')  // 每天凌晨2点
    }
    
    tools {
        jdk 'JDK17'
        maven 'Maven3.9'
    }
    
    stages {
        stage('代码检出') {
            steps {
                checkout scm
                sh 'git log --oneline -5'
            }
        }
        
        stage('编译构建') {
            steps {
                sh 'mvn clean package -DskipTests'
            }
        }
        
        stage('单元测试') {
            steps {
                sh 'mvn test'
            }
            post {
                always {
                    junit 'target/surefire-reports/**/*.xml'
                }
            }
        }
        
        stage('代码扫描') {
            steps {
                // SonarQube扫描
                withSonarQubeEnv('SonarServer') {
                    sh 'mvn sonar:sonar'
                }
            }
        }
        
        stage('构建镜像') {
            steps {
                sh """
                    docker build \
                        -t ${DOCKER_REGISTRY}/${IMAGE_NAME}:${VERSION} \
                        -t ${DOCKER_REGISTRY}/${IMAGE_NAME}:latest \
                        --build-arg JAR_FILE=target/*.jar \
                        .
                """
            }
        }
        
        stage('推送镜像') {
            steps {
                withCredentials([usernamePassword(
                    credentialsId: 'harbor-creds',
                    usernameVariable: 'HARBOR_USER',
                    passwordVariable: 'HARBOR_PASS')]) {
                    sh """
                        echo ${HARBOR_PASS} | docker login ${DOCKER_REGISTRY} \
                            -u ${HARBOR_USER} --password-stdin
                        docker push ${DOCKER_REGISTRY}/${IMAGE_NAME}:${VERSION}
                        docker push ${DOCKER_REGISTRY}/${IMAGE_NAME}:latest
                    """
                }
            }
        }
        
        stage('部署到K8S') {
            steps {
                sh """
                    kubectl set image deployment/order-service \
                        order-service=${DOCKER_REGISTRY}/${IMAGE_NAME}:${VERSION} \
                        -n production
                    kubectl rollout status deployment/order-service \
                        -n production --timeout=300s
                """
            }
        }
    }
    
    post {
        success {
            dingtalk(robot: 'jenkins-bot',
                type: 'MARKDOWN',
                title: '构建成功',
                text: ["✅ ${env.JOB_NAME} #${VERSION} 部署成功"])
        }
        failure {
            dingtalk(robot: 'jenkins-bot',
                type: 'MARKDOWN',
                title: '构建失败',
                text: ["❌ ${env.JOB_NAME} #${VERSION} 部署失败"])
        }
        always {
            cleanWs()  // 清理工作空间
        }
    }
}

2. GitLab CI


# .gitlab-ci.yml
stages:
  - build
  - test
  - package
  - deploy

variables:
  MAVEN_CLI_OPTS: "-s .m2/settings.xml --batch-mode"
  DOCKER_REGISTRY: "harbor.company.com"

# 缓存Maven依赖
cache:
  key: ${CI_COMMIT_REF_SLUG}
  paths:
    - .m2/repository/

# ====== Build Stage ======
build:
  stage: build
  image: maven:3.9-eclipse-temurin-17
  script:
    - mvn $MAVEN_CLI_OPTS compile
  artifacts:
    paths:
      - target/
    expire_in: 1 hour

# ====== Test Stage ======
test:
  stage: test
  image: maven:3.9-eclipse-temurin-17
  script:
    - mvn $MAVEN_CLI_OPTS test
  coverage: '/Total.*?([0-9]{1,3})%/'  # 提取覆盖率
  artifacts:
    reports:
      junit:
        - target/surefire-reports/TEST-*.xml

# ====== Package Stage ======
docker-build:
  stage: package
  image: docker:24
  services:
    - docker:24-dind
  before_script:
    - echo $HARBOR_PASSWORD | docker login -u $HARBOR_USER --password-stdin $DOCKER_REGISTRY
  script:
    - |
      docker build \
        -t $DOCKER_REGISTRY/app/order-service:$CI_COMMIT_SHORT_SHA \
        -t $DOCKER_REGISTRY/app/order-service:latest .
    - docker push $DOCKER_REGISTRY/app/order-service:$CI_COMMIT_SHORT_SHA
    - docker push $DOCKER_REGISTRY/app/order-service:latest
  only:
    - main
    - tags

# ====== Deploy Stage ======
deploy-prod:
  stage: deploy
  image: bitnami/kubectl
  script:
    - kubectl config use-context production
    - |
      kubectl set image deployment/order-service \
        order-service=$DOCKER_REGISTRY/app/order-service:$CI_COMMIT_SHORT_SHA \
        -n production
    - kubectl rollout status deployment/order-service -n production
  environment:
    name: production
    url: https://app.example.com
  only:
    - tags
  when: manual   # 手动触发部署

3. 部署策略对比


蓝绿部署(Blue-Green):

  ┌─────────────┐     ┌─────────────┐
  │  Blue(旧版)   │     │  Green(新版)  │
  │  v1.0        │     │  v2.0        │
  │  3 replicas  │     │  3 replicas  │
  └──────┬───────┘     └──────┬───────┘
         │                    │
    ┌────┴────────────────────┴────┐
    │        Load Balancer         │
    │  当前指向: Blue ──切换──▶ Green │
    └──────────────────────────────┘
    
  特点:全量切换,瞬时完成,回滚快(切回来即可)
  缺点:需要双倍资源

金丝雀发布(Canary):

  ┌─────────────┐     ┌─────────────┐
  │  Stable(旧版) │     │  Canary(新版) │
  │  v1.0        │     │  v2.0        │
  │  9 replicas  │     │  1 replica   │
  └──────┬───────┘     └──────┬───────┘
         │  90%流量            │  10%流量
         │                    │
    ┌────┴────────────────────┴────┐
    │        Load Balancer         │
    │  金丝雀占比: 10% → 50% → 100% │
    └──────────────────────────────┘
    
  特点:渐进式发布,风险可控,可观测
  缺点:发布周期长,需要流量染色能力

K8S中的金丝雀发布实现:


# 方案1:调整Deployment副本数
# stable: 9 replicas, canary: 1 replica → 10%流量到新版

# 方案2:使用Istio VirtualService精确控制
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
spec:
  http:
    - route:
        - destination:
            host: order-service
            subset: stable
          weight: 90
        - destination:
            host: order-service
            subset: canary
          weight: 10

4. 镜像版本管理


镜像Tag策略:

  ✅ 推荐:
  ├── Git SHA:     order-service:abc1234     (可追溯,唯一)
  ├── 语义版本:     order-service:v1.2.0      (正式发布)
  └── 流水线号:     order-service:build-123   (CI/CD标识)

  ❌ 不推荐:
  ├── latest:      无法追溯版本,缓存问题
  └── 无Tag:       完全不可控

版本管理最佳实践:

  开发分支(feature) → 构建镜像: feature-abc123
  合并到main       → 构建镜像: main-def456
  打Tag(v1.2.0)   → 构建镜像: v1.2.0
  部署到生产        → 使用语义版本Tag
  
  K8S Deployment中:
  image: harbor.company.com/app/order-service:v1.2.0
  不要用latest,不要用:no-tag

5. 与工作实战对照


你工作中的CI/CD流程:

  Git Push → Jenkins触发
    │
    ├── mvn package (Java 17)
    ├── docker build (ARM64架构)
    │   └── FROM --platform=linux/arm64 ...
    ├── docker push (Harbor私有仓库)
    └── kubectl apply (K8S集群)
        └── kubectl rollout status
  
  特殊处理:
  ├── ARM64镜像构建: buildx多平台
  ├── Harbor认证: imagePullSecrets
  └── 多环境: dev/staging/production

面试速记卡(考前30秒速看)

练习题(自测)

1. Jenkins Pipeline中post块和stage内post块的区别?

2. GitLab CI的only和rules有什么区别?哪个更推荐?

3. 蓝绿部署和金丝雀发布的资源开销对比?

4. 为什么生产环境不建议用latest Tag?

5. 如何在Jenkins中实现多环境(dev/staging/prod)的差异化部署?

学习资料