Jenkins vs GitLab CI：两大CI/CD平台的深度对比与选型指南

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

pipeline {
    agent any

    environment {
        NODE_VERSION = '20'
        APP_NAME = 'myapp'
    }

    stages {
        stage('Checkout') {
            steps {
                checkout scm
            }
        }

        stage('Install') {
            agent {
                docker {
                    image "node:${NODE_VERSION}"
                }
            }
            steps {
                sh 'npm ci'
            }
        }

        stage('Test') {
            parallel {
                stage('Unit Tests') {
                    steps {
                        sh 'npm run test:unit'
                    }
                }
                stage('E2E Tests') {
                    steps {
                        sh 'npm run test:e2e'
                    }
                }
            }
        }

        stage('Build') {
            when {
                branch 'main'
            }
            steps {
                sh 'npm run build'
                archiveArtifacts artifacts: 'dist/**'
            }
        }

        stage('Deploy') {
            when {
                tag pattern: "v\\d+\\.\\d+\\.\\d+", comparator: "REGEXP"
            }
            steps {
                sh './deploy.sh'
            }
        }
    }

    post {
        success {
            emailext(
                subject: "构建成功: ${env.JOB_NAME}",
                body: "构建 ${env.BUILD_NUMBER} 成功完成",
                to: "team@example.com"
            )
        }
        failure {
            emailext(
                subject: "构建失败: ${env.JOB_NAME}",
                body: "构建 ${env.BUILD_NUMBER} 失败",
                to: "team@example.com"
            )
        }
    }
}

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102

# 全局变量
variables:
  NODE_VERSION: "20"
  APP_NAME: "myapp"
  DOCKER_DRIVER: overlay2
  DOCKER_TLS_CERTDIR: "/certs"

# 定义阶段
stages:
  - build
  - test
  - deploy

# 默认配置
default:
  image: node:${NODE_VERSION}
  cache:
    key: ${CI_COMMIT_REF_SLUG}
    paths:
      - node_modules/
  before_script:
    - npm ci

# 构建作业
build:
  stage: build
  script:
    - npm run build
  artifacts:
    paths:
      - dist/
    expire_in: 1 week
  only:
    - main
    - merge_requests

# 单元测试
unit-test:
  stage: test
  script:
    - npm run test:unit
  coverage: '/All files[^|]*\|[^|]*\s+([\d\.]+)/'
  artifacts:
    reports:
      coverage_report:
        coverage_format: cobertura
        path: coverage/cobertura-coverage.xml

# E2E测试
e2e-test:
  stage: test
  image: mcr.microsoft.com/playwright:v1.40.0
  script:
    - npm ci
    - npx playwright install --with-deps
    - npm run test:e2e
  artifacts:
    when: always
    paths:
      - playwright-report/
    expire_in: 30 days

# 并行测试矩阵
test-matrix:
  stage: test
  parallel:
    matrix:
      - NODE_VERSION: [18, 20, 21]
  image: node:${NODE_VERSION}
  script:
    - npm run test

# 部署到开发环境
deploy:dev:
  stage: deploy
  script:
    - ./deploy.sh dev
  environment:
    name: development
    url: https://dev.example.com
  only:
    - develop

# 部署到生产环境
deploy:prod:
  stage: deploy
  script:
    - ./deploy.sh prod
  environment:
    name: production
    url: https://example.com
  when: manual  # 手动触发
  only:
    - tags
    - /^v\d+\.\d+\.\d+$/

# 通知
notify:
  stage: .post
  script:
    - curl -X POST $SLACK_WEBHOOK -d '{"text":"Pipeline ${CI_PIPELINE_ID} 完成"}'
  when: always

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41

# 1. 复杂的遗留项目
需要与各种旧系统集成：
- Ant、Maven、Gradle构建
- 自定义构建脚本
- 多种部署方式

# 2. 高度定制化需求
pipeline {
    agent none

    stages {
        stage('动态并行构建') {
            matrix {
                axes {
                    axis {
                        name 'PLATFORM'
                        values 'linux', 'windows', 'macos'
                    }
                    axis {
                        name 'ARCH'
                        values 'x64', 'arm64'
                    }
                }
                stages {
                    stage('Build') {
                        agent { label "${PLATFORM}-${ARCH}" }
                        steps {
                            sh "./build-${PLATFORM}-${ARCH}.sh"
                        }
                    }
                }
            }
        }
    }
}

# 3. 多语言、多技术栈项目
可通过插件支持几乎所有技术

# 4. 需要精细控制构建流程
Groovy脚本提供强大的编程能力

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

# 1. 现代化云原生项目
features:
  - Kubernetes原生集成
  - Docker Registry内置
  - Terraform状态管理
  - 容器扫描

# 2. 敏捷团队协作
workflow:
  - 代码审查集成
  - Merge Request触发
  - 实时构建状态显示
  - 讨论与构建关联

# 3. 微服务架构
services:
  mysql:
    image: mysql:8.0
  redis:
    image: redis:alpine

test-service:
  services:
    - mysql
    - redis
  script:
    - npm test

# 4. DevOps一体化
从代码到部署全流程：
git push → 自动测试 → 自动部署 → 监控

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

# Master内存需求
最小配置: 512MB
推荐配置: 4GB+ (大规模部署)

# Agent内存需求
每个Agent: 1-2GB

# 插件开销
每个活跃插件: 50-200MB
典型安装: 50+ plugins = 额外2-10GB

# 总资源估算
小型团队: 8GB RAM, 4 CPU
中型团队: 16GB RAM, 8 CPU
大型团队: 32GB+ RAM, 16+ CPU

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18

# GitLab Server内存需求
最小配置: 4GB
推荐配置: 8GB+

# Runner资源需求
Shared Runner: 由GitLab托管
Self-hosted Runner: 1-2GB per instance

# 无插件开销
功能内置，无额外内存占用

# 总资源估算
小型团队: 8GB RAM, 4 CPU
中型团队: 16GB RAM, 8 CPU
大型团队: 32GB+ RAM, 16+ CPU

# 优势：Runner可独立扩展
无需增加GitLab Server资源

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11

// 构建启动时间
冷启动: 30-60秒 (Master + Agent初始化)
热启动: 5-10秒 (Agent已就绪)

// 分布式构建优势
可并行运行多个Agent
适合大型项目的并行构建

// 示例：100个测试用例
串行: 10分钟
并行(10个Agent): 1分钟

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17

# 构建启动时间
冷启动: 10-20秒 (Runner快速启动)
热启动: 2-5秒 (Runner常驻)

# Pipeline执行效率
Pipeline解析: <1秒
作业调度: 实时

# 示例：100个测试用例
串行: 10分钟
并行(10个Runner): 1分钟

# 优势：Pipeline级别的缓存
cache:
  paths:
    - node_modules/
  key: ${CI_COMMIT_REF_SLUG}

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

# 1. 转换Jenkinsfile到.gitlab-ci.yml

# Jenkins (Before)
pipeline {
    agent { docker 'node:20' }
    stages {
        stage('Test') {
            steps {
                sh 'npm test'
            }
        }
    }
}

# GitLab CI (After)
test:
  image: node:20
  script:
    - npm test

# 2. 环境变量迁移
# Jenkins
environment {
    NODE_ENV = 'production'
    API_KEY = credentials('api-key')
}

# GitLab CI
variables:
  NODE_ENV: production
  API_KEY: ${API_KEY}  # 从GitLab CI/CD变量读取

# 3. Secret管理
# Jenkins: Credentials存储
withCredentials([string(credentialsId: 'api-key', variable: 'API_KEY')]) {
    sh 'docker build --build-arg API_KEY=$API_KEY .'
}

# GitLab CI: Masked Variables
variables:
  API_KEY: ${MASKED_API_KEY}
# Settings → CI/CD → Variables → Add Variable → Masked

# 4. 并行作业转换
# Jenkins
parallel(
    "Test-Node-18": { sh 'docker-compose run test-node18' },
    "Test-Node-20": { sh 'docker-compose run test-node20' }
)

# GitLab CI
test:
  parallel:
    matrix:
      - NODE_VERSION: [18, 20]
  image: node:${NODE_VERSION}
  script:
    - npm test

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22

# 场景：大型企业的最佳实践
使用Jenkins处理：
  - 复杂的构建流程
  - 遗留系统集成
  - 多阶段部署流程

使用GitLab CI处理：
  - 现代化应用
  - 微服务部署
  - 快速迭代项目

# 集成方案
# GitLab CI 触发 Jenkins Job
trigger-jenkins:
  stage: build
  script:
    - |
      curl -X POST "${JENKINS_URL}/job/${JOB_NAME}/buildWithParameters" \
        --user "${JENKINS_USER}:${JENKINS_TOKEN}" \
        --data "BRANCH=${CI_COMMIT_REF_NAME}&COMMIT=${CI_COMMIT_SHA}"
  only:
    - main