GitHub Actions 实现 CI/CD 自动化部署
Published in：2026-05-14 |
Words: 1.8k | Reading time: 9min | reading：

概述

本文介绍如何使用 GitHub Actions 构建完整的 CI/CD 流水线，以实际项目为例，涵盖核心概念、配置实践、故障排查和优化建议。

一、CI/CD 概念解析

1.1 核心定义

概念 定义 核心职责
CI（持续集成） 代码提交后自动执行构建与测试 代码质量保障、早期问题发现
CD（持续部署） 构建产物自动部署到目标环境 环境一致性、快速交付

1.2 典型工作流

1
代码提交 → 触发事件 → 环境准备 → 依赖安装 → 测试执行 → 构建打包 → 部署发布

二、GitHub Actions 核心概念

2.1 组件层次

1
2
3
4
5
Workflow（工作流）
    ├── Event（触发事件）
    └── Jobs（任务集合）
            └── Steps（步骤序列）
                    └── Actions（动作/命令）

2.2 关键术语

  • Workflow：定义在 .github/workflows/*.yml，描述完整的自动化流程
  • Event：触发条件，支持 push、pull_request、schedule 等
  • Job：独立运行单元，可配置并行或依赖关系
  • Step：Job 内的执行单元，支持脚本或复用 Actions
  • Runner：执行环境，支持 GitHub Hosted 或 Self-Hosted

三、实战配置：AI 项目 CI/CD 流水线

3.1 目录结构

1
2
3
4
5
6
7
├── .github/
│   └── workflows/
│       └── main.yml          # 主工作流配置
├── src/                      # 源代码目录
├── tests/                    # 测试代码目录
├── Dockerfile                # 容器构建配置
└── requirements.txt          # Python 依赖声明

3.2 完整配置示例

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
name: AI-Project-CI

on:
  push:
    branches: [ main, develop ]
  pull_request:
    branches: [ main ]

jobs:
  build-and-test:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        python-version: [3.9, 3.10]
    
    steps:
      - name: Checkout code
        uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Set up Python ${{ matrix.python-version }}
        uses: actions/setup-python@v5
        with:
          python-version: ${{ matrix.python-version }}
          cache: 'pip'

      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install -r requirements.txt

      - name: Run unit tests
        run: pytest tests/unit/ -v --cov=src/

      - name: Build Docker image
        if: github.ref == 'refs/heads/main'
        run: |
          docker build . -t ${{ secrets.DOCKER_REGISTRY }}/anime-detect:${{ github.sha }}
          docker login -u ${{ secrets.DOCKER_USER }} -p ${{ secrets.DOCKER_TOKEN }}
          docker push ${{ secrets.DOCKER_REGISTRY }}/anime-detect:${{ github.sha }}

  deploy:
    needs: build-and-test
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main'
    
    steps:
      - name: Deploy to production
        uses: appleboy/ssh-action@v1.0.3
        with:
          host: ${{ secrets.SSH_HOST }}
          username: ${{ secrets.SSH_USER }}
          key: ${{ secrets.SSH_PRIVATE_KEY }}
          script: |
            docker pull ${{ secrets.DOCKER_REGISTRY }}/anime-detect:${{ github.sha }}
            docker stop anime-detect || true
            docker rm anime-detect || true
            docker run -d --name anime-detect -p 80:80 \
              -e REDIS_HOST=${{ secrets.REDIS_HOST }} \
              ${{ secrets.DOCKER_REGISTRY }}/anime-detect:${{ github.sha }}

四、常见问题与解决方案

4.1 依赖安装失败

问题现象：libgl1-mesa-glx 包无法安装

原因分析：Debian 12+ 版本中包名变更

解决方案：

1
2
3
4
5
6
7
8
9
10
11
12
# Dockerfile 正确配置
FROM python:3.9-slim

RUN apt-get update && apt-get install -y \
    libgl1 \
    libglib2.0-0 \
    gcc \
    && rm -rf /var/lib/apt/lists/*

WORKDIR /app
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt

4.2 敏感信息泄露

问题现象：密码等敏感信息出现在日志中

解决方案：使用 GitHub Secrets 管理敏感数据

1
2
3
4
5
6
# 在 GitHub Secrets 中配置以下变量
# DOCKER_USER, DOCKER_TOKEN, SSH_HOST, SSH_USER, SSH_PRIVATE_KEY

# 在 workflow 中引用
env:
  DATABASE_URL: ${{ secrets.DATABASE_URL }}

4.3 构建时间过长

优化方案：启用缓存机制

1
2
3
4
5
6
7
8
9
- name: Cache pip dependencies
  uses: actions/cache@v4
  with:
    path: |
      ~/.cache/pip
      **/__pycache__
    key: ${{ runner.os }}-python-${{ matrix.python-version }}-${{ hashFiles('requirements.txt') }}
    restore-keys: |
      ${{ runner.os }}-python-${{ matrix.python-version }}-

五、日志分析与调试

5.1 日志访问路径

1
GitHub Repository → Actions → 选择 Workflow → 选择 Run → 查看 Job 日志

5.2 常见错误码

错误码 含义 排查方向
exit code 1 命令执行失败 检查脚本语法和依赖
exit code 137 内存不足 增加 Runner 资源或优化代码
Connection refused 网络连接失败 检查网络策略和目标服务状态

5.3 调试技巧

  1. 使用 set -x 启用命令调试
  2. 添加 echo 输出关键变量值
  3. 使用 tmate 进行交互式调试

六、运行效果示例

6.1 成功执行效果

当工作流成功执行时，GitHub Actions 会显示以下状态：

Actions 页面概览：

1
2
3
4
5
6
7
8
✓ AI-Project-CI
  push · main
  1 hour ago · in 2m 35s
  
  Jobs:
    ✅ build-and-test (Python 3.9)
    ✅ build-and-test (Python 3.10)  
    ✅ deploy

测试步骤输出示例：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
Run pytest tests/unit/ -v --cov=src/
============================= test session starts ==============================
platform linux -- Python 3.9.17, pytest-7.4.0, pluggy
rootdir: /home/runner/work/anime-detect/anime-detect
collected 24 items

tests/unit/test_detect.py::test_load_model PASSED                       [  4%]
tests/unit/test_detect.py::test_image_preprocess PASSED                  [  8%]
tests/unit/test_detect.py::test_detect_anime PASSED                      [ 12%]
...
tests/unit/test_api.py::test_health_check PASSED                         [ 95%]
tests/unit/test_api.py::test_inference_endpoint PASSED                   [100%]

---------- coverage: platform linux, python 3.9.17-final-0 ----------
Name                      Stmts   Miss  Cover
---------------------------------------------
src/detect.py               120      5    96%
src/api.py                   85      3    96%
src/utils.py                 45      0   100%
---------------------------------------------
TOTAL                       250      8    97%

============================= 24 passed in 15.23s ==============================

Docker 构建输出示例：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Run docker build . -t registry.example.com/anime-detect:abc123
Sending build context to Docker daemon  156.2MB

Step 1/6 : FROM python:3.9-slim
 ---> 8a955d570e80
Step 2/6 : RUN apt-get update && apt-get install -y libgl1 libglib2.0-0 gcc
 ---> Using cache
 ---> abc123456789
Step 3/6 : WORKDIR /app
 ---> Using cache
 ---> def098765432
Step 4/6 : COPY requirements.txt .
 ---> Using cache
 ---> 123456789abc
Step 5/6 : RUN pip install --no-cache-dir -r requirements.txt
 ---> Using cache
 ---> 987654321def
Step 6/6 : COPY . .
 ---> 0123456789ab
Successfully built 0123456789ab
Successfully tagged registry.example.com/anime-detect:abc123

6.2 失败执行效果

测试失败示例：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Run pytest tests/unit/ -v --cov=src/
...
tests/unit/test_detect.py::test_detect_anime FAILED                     [ 12%]

=================================== FAILURES ===================================
___________________________ test_detect_anime ___________________________

def test_detect_anime():
    model = load_model()
    result = model.predict(test_image)
    
>   assert result['confidence'] > 0.9
E   AssertionError: assert 0.85 > 0.9
E    +  where 0.85 = {'label': 'Sailor Moon', 'confidence': 0.85}['confidence']

tests/unit/test_detect.py:23: AssertionError
============================= 1 failed, 23 passed in 14.87s ======================
Error: Process completed with exit code 1

依赖安装失败示例：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Run pip install -r requirements.txt
Collecting torch==2.0.1
  Downloading torch-2.0.1-cp39-none-linux_x86_64.whl (172.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 172.3/172.3 MB 45.2 MB/s
Collecting opencv-python==4.7.0.72
  Downloading opencv-python-4.7.0.72.tar.gz (88.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 88.3/88.3 MB 42.1 MB/s
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error
  
  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [55 lines of output]
      error: OpenCV requires 'numpy>=1.21.2' but you have numpy 1.19.5 installed.
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
Error: Process completed with exit code 1

6.3 时间统计示例

步骤 耗时 状态
Checkout code 15s ✅
Set up Python 8s ✅
Install dependencies 45s ✅
Run unit tests 1min 20s ✅
Build Docker image 3min 10s ✅
Deploy to production 45s ✅
总计 5min 43s ✅

七、进阶配置

7.1 多环境部署

1
2
3
4
5
6
7
8
9
10
11
12
jobs:
  deploy-staging:
    runs-on: ubuntu-latest
    environment: staging
    steps: [...]

  deploy-production:
    needs: deploy-staging
    runs-on: ubuntu-latest
    environment: production
    environment_url: https://api.example.com
    steps: [...]

6.2 定时任务

1
2
3
on:
  schedule:
    - cron: '0 2 * * *'  # 每天凌晨 2 点执行

6.3 矩阵构建

1
2
3
4
strategy:
  matrix:
    os: [ubuntu-latest, windows-latest]
    python-version: ["3.9", "3.10", "3.11"]

七、最佳实践

  1. 分层设计：将测试、构建、部署分离为独立 Job
  2. 环境隔离：使用 Environment 功能管理不同部署环境
  3. 安全优先：所有敏感信息通过 Secrets 管理
  4. 缓存优化：合理使用缓存减少重复操作
  5. 失败通知：配置 Slack/钉钉等即时通知
  6. 权限最小化：限制 GitHub Token 权限范围

总结

GitHub Actions 提供了强大的自动化能力，通过合理配置可以实现从代码提交到生产部署的全流程自动化。关键在于理解组件模型、掌握配置语法，并结合项目特点进行优化。

参考链接：

GitHub Actions CI/CD DevOps 自动化部署
Prev:
Supervisord 在 Python 微服务项目中的应用
Next:
Kubernetes部署python程序

    • Copyright © 2023 - Now Zhaoqi.Cao | Powered by Hexo | Theme Bamboo

    Total visits： times |