从GitHub Actions迁移至Jenkins Pipeline时环境变量加载问题求助

当前流水线存在多个核心问题，导致DATABASE_URL无法正确传递到Docker构建流程，进而影响Prisma迁移执行，同时部分步骤的变量引用、阶段顺序也存在不规范之处。以下是针对性的修复方案：

1. 调整阶段顺序，确保环境文件正确落地 #

原流水线先加载环境变量再拉取代码，会导致拉取的代码覆盖当前目录的文件，无法将.env放到项目目录供Prisma使用。必须将Checkout Code放到Load Environment之前：

stages {
    stage('Checkout Code') {
        steps {
            git branch: 'dev',
                url: 'my_github_url.git',
                credentialsId: 'my_credentail_id'
        }
    }

    stage('Load Environment') {
        steps {
            script {
                withCredentials([file(credentialsId: 'my_credentail_id', variable: 'ENV_FILE')]) {
                    // 把凭证中的.env文件复制到项目根目录
                    sh "cp ${ENV_FILE} ./.env"
                    // 加载变量到Jenkins全局环境，供后续步骤调用
                    def envVars = readProperties file: '.env'
                    envVars.each { key, value ->
                        env["${key}"] = value
                    }
                }
            }
        }
    }
}

2. 修复Docker构建的参数传递 #

如果Dockerfile需要用DATABASE_URL作为构建参数，要确保变量引用正确，同时在Dockerfile中声明该参数：

流水线中构建镜像的代码： #

stage('Building image') {
    steps {
        script {
            def buildArgs = "--build-arg DATABASE_URL=${env.DATABASE_URL}"
            docker.build("${registry}:dev_latest", "${buildArgs} .")
            echo "Build successful"
        }
    }
}

Dockerfile中对应的配置： #

ARG DATABASE_URL
# 将构建参数转为容器内环境变量，供Prisma使用
ENV DATABASE_URL=${DATABASE_URL}

# 执行Prisma迁移
RUN npx prisma migrate deploy

3. 修正Shell脚本的变量引用 #

原脚本使用单引号'会阻止Jenkins变量解析，统一改用双引号"：

stage('Configure AWS Credentials') {
    steps {
        sh """
            aws configure set aws_access_key_id ${env.AWS_ACCESS_KEY_ID}
            aws configure set aws_secret_access_key ${env.AWS_SECRET_ACCESS_KEY}
            aws configure set region us-east-1
        """
    }
}

stage('Login to ECR') {
    steps {
        sh """
            aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin ${env.registry}
        """
    }
}

更规范的方式：使用Jenkins AWS Credentials插件，避免手动配置凭证：

stage('Configure AWS Credentials') {
    steps {
        withAWS(credentials: 'aws-credentials-id', region: 'us-east-1') {
            echo "AWS credentials configured"
        }
    }
}

4. 修复镜像推送与部署逻辑 #

镜像推送要确保和构建的标签一致，部署阶段的变量引用也要修正：

stage('Push Docker Image') {
    steps {
        sh "docker push ${registry}:dev_latest"
    }
}

stage('Deploy to Development Server') {
    steps {
        sshagent(['jenkins-ssh-key']) {
            sh """
                ssh -o StrictHostKeyChecking=no ${env.USERNAME}@${env.HOST_NAME_DEV} '
                    sudo docker system prune -a -f
                    sudo docker pull ${env.registry}/project:dev_latest
                    cd /home/ubuntu/project
                    bash docker-pull.sh
                '
            """
        }
    }
}

完整修正后的流水线代码 #

pipeline {
    agent any

    environment {
        registry = "my_ecr_registry"
    }

    stages {
        stage('Checkout Code') {
            steps {
                git branch: 'dev',
                    url: 'my_github_url.git',
                    credentialsId: 'my_credentail_id'
            }
        }

        stage('Load Environment') {
            steps {
                script {
                    withCredentials([file(credentialsId: 'my_credentail_id', variable: 'ENV_FILE')]) {
                        sh "cp ${ENV_FILE} ./.env"
                        def envVars = readProperties file: '.env'
                        envVars.each { key, value ->
                            env["${key}"] = value
                        }
                    }
                }
            }
        }

        stage('Print All Environment Variables') {
            steps {
                sh 'env'
            }
        }

        stage('Building image') {
            steps {
                script {
                    def buildArgs = "--build-arg DATABASE_URL=${env.DATABASE_URL}"
                    docker.build("${registry}:dev_latest", "${buildArgs} .")
                    echo "Build successful"
                }
            }
        }

        stage('Configure AWS Credentials') {
            steps {
                withAWS(credentials: 'aws-credentials-id', region: 'us-east-1') {
                    echo "AWS credentials configured"
                }
            }
        }

        stage('Login to ECR') {
            steps {
                sh """
                    aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin ${env.registry}
                """
            }
        }

        stage('Push Docker Image') {
            steps {
                sh "docker push ${registry}:dev_latest"
            }
        }

        stage('Deploy to Development Server') {
            steps {
                sshagent(['jenkins-ssh-key']) {
                    sh """
                        ssh -o StrictHostKeyChecking=no ${env.USERNAME}@${env.HOST_NAME_DEV} '
                            sudo docker system prune -a -f
                            sudo docker pull ${env.registry}/project:dev_latest
                            cd /home/ubuntu/project
                            bash docker-pull.sh
                        '
                    """
                }
            }
        }
    }
}

关键说明 #

• 用readProperties替代手动解析.env，避免换行符、空格等解析错误
• 确保.env文件被放到项目根目录，Prisma可直接读取
• 所有Shell脚本使用双引号，保证Jenkins环境变量被正确解析

内容的提问来源于stack exchange，提问作者ajay