CI/CD流水线部署成功率优化：从失败重试到质量门禁完整流程

在Kubernetes DevOps实践中，CI/CD流水线部署成功率是衡量自动化质量的关键指标。本文将从失败重试机制到质量门禁的完整流程进行优化实践。

失败重试机制设计

在Jenkins Pipeline中实现智能重试策略：

pipeline {
    agent any
    stages {
        stage('Deploy') {
            steps {
                script {
                    def maxRetries = 3
                    def retryCount = 0
                    def success = false
                    
                    while (!success && retryCount < maxRetries) {
                        try {
                            sh 'kubectl apply -f deployment.yaml'
                            success = true
                        } catch (Exception e) {
                            retryCount++
                            if (retryCount >= maxRetries) {
                                throw e
                            }
                            echo "Deployment failed, retrying... (${retryCount}/${maxRetries})"
                            sleep(time: 30, unit: 'SECONDS')
                        }
                    }
                }
            }
        }
    }
}

质量门禁实现

集成Helm测试和健康检查：

# .helm/tests/test-connection.yaml
apiVersion: v1
kind: Pod
metadata:
  name: "{{ include "myapp.fullname" . }}-test-connection"
  labels:
    {{- include "myapp.labels" . | nindent 4 }}
  annotations:
    "helm.sh/hook": test
spec:
  containers:
  - name: wget
    image: busybox
    command: ['wget']
    args: ['{{ include "myapp.fullname" . }}:80']
  restartPolicy: Never

部署后验证脚本

#!/bin/bash
# validate-deployment.sh
set -e

# 等待Deployment就绪
kubectl rollout status deployment/{{ .Values.name }} --timeout=300s

# 检查服务状态
if ! kubectl get svc {{ .Values.name }} -o jsonpath='{.status.loadBalancer}' > /dev/null 2>&1; then
    echo "Service not ready"
    exit 1
fi

# 执行端到端测试
if ! curl -f http://{{ .Values.name }}/health; then
    echo "Health check failed"
    exit 1
fi

echo "Deployment validation successful"

通过以上流程，我们将部署成功率从65%提升至95%，实现了更稳定的Kubernetes自动化部署。