前端 CI/CD 流程与自动化部署实践

GitLab CI 配置

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

test:
  stage: test
  image: node:16
  script:
    - npm install
    - npm test
  only:
    - main

build:
  stage: build
  image: node:16
  script:
    - npm install
    - npm run build
  artifacts:
    paths:
      - build/
  only:
    - main

deploy:
  stage: deploy
  image: alpine:latest
  script:
    - apk add --no-cache rsync openssh
    - mkdir -p ~/.ssh
    - echo "$SSH_PRIVATE_KEY" > ~/.ssh/id_rsa
    - chmod 600 ~/.ssh/id_rsa
    - ssh-keyscan -H $REMOTE_HOST >> ~/.ssh/known_hosts
    - rsync -avz --delete build/ $REMOTE_USER@$REMOTE_HOST:$REMOTE_TARGET
    - ssh $REMOTE_USER@$REMOTE_HOST "sudo systemctl restart nginx"
  only:
    - main
  environment:
    name: production

Jenkins 配置

// Jenkinsfile
pipeline {
  agent any
  stages {
    stage('Checkout') {
      steps {
        checkout scm
      }
    }
    stage('Install Dependencies') {
      steps {
        sh 'npm install'
      }
    }
    stage('Test') {
      steps {
        sh 'npm test'
      }
    }
    stage('Build') {
      steps {
        sh 'npm run build'
      }
    }
    stage('Deploy') {
      steps {
        sh '''
          scp -r build/* user@server:/var/www/html/
          ssh user@server "sudo systemctl restart nginx"
        '''
      }
    }
  }
  post {
    always {
      echo 'Pipeline completed'
    }
    success {
      echo 'Deployment successful'
    }
    failure {
      echo 'Deployment failed'
    }
  }
}

环境变量配置

# .env
# 服务器配置
REMOTE_HOST=your-server.com
REMOTE_USER=deploy
REMOTE_TARGET=/var/www/html/

# SSH 密钥（在 CI/CD 平台的 Secrets 中配置，切勿提交至仓库）
# SSH_PRIVATE_KEY=your-ssh-private-key

最佳实践与注意事项

CI/CD 能显著提升效率，但需避免过度配置。常见问题包括：

1. 调试成本：配置复杂可能导致排查问题比手动部署更耗时。
2. 流程冗余：包含不必要的步骤会延长部署时间，应仅运行相关测试。
3. 适度原则：大型项目必不可少，小型项目需权衡维护成本。
4. 核心目标：目的是提高效率和可靠性，而非炫技。如果配置导致变慢或不可靠，则视为失败。

务必根据实际项目规模和需求平衡自动化程度，确保配置安全且高效。