看起来标题（* 如何根据执行结果在Jenkins Pipeline中设置当前构建结果？）与代码示例（ 如何根据该文件的内容分别将currentBuild.result设置为“SUCCESS”或“FAILURE”？*）有点不同
在像您这样的声明性管道中，可以使用catchError块根据命令执行结果轻松设置当前构建（和阶段）结果。例如，将阶段设置为FAILURE，将整个作业设置为UNSTABLE：

catchError(buildResult: 'UNSTABLE', stageResult: 'FAILURE') {
    command ...
}

我不知道有什么简洁的一行程序可以直接从文件内容设置构建/阶段结果（身体的问题）。但我想你可以在将状态消息写入文件时，应该设置start_up.sh脚本的正确退出代码，因此在将"SUCCESSFUL"写入文件时，可以使用零代码退出脚本，但是当写"ERROR"时，你可以用非零代码退出，这就足够让流水线处理catchError块了。

这是我在一些gitlab集成项目中使用的一个例子...但是使用的是脚本化的管道。当构建失败时会有电子邮件通知，当它恢复稳定时也会有电子邮件通知。

/* documentation pour les appels gitlab:
 https://github.com/jenkinsci/gitlab-plugin#configuring-access-to-gitlab

Toujours utiliser la syntaxe scripted pipeline (et non declarative, merci)
Please read the fucking manual:
https://github.com/jenkinsci/gitlab-plugin
*/
// Reference the GitLab connection name from your Jenkins Global configuration (http://JENKINS_URL/configure, GitLab section)

 if (env.BRANCH_NAME != 'developpement') {
      properties([gitLabConnection('numagit'),
        buildDiscarder(
            logRotator(
                numToKeepStr: '1',artifactNumToKeepStr: '1'
            )
        )
        ]
        )
    }
  else {
       properties([gitLabConnection('numagit'),
        buildDiscarder(
            logRotator(
                numToKeepStr: '5',artifactNumToKeepStr: '1'
            )
        )
    ]
)
  }

    node {
    try {
         stage('Checkout sources') {

                echo 'Checkout..'
                checkout scm
         }
         
         
         gitlabBuilds(builds: [
                            "Compiling linux64", 
                            "Compiling linux 32 bits",
                            "Compiling win32",
                            "Deploy"
                            ]) {

         
    try {
        stage('Compiling linux64') {
            gitlabCommitStatus("Compiling linux64") {
                ...
            }
        }
    } catch (e) {
       currentBuild.result = "FAILURE" // make sure other exceptions are recorded as failure too
    }
        
    stage('Compiling linux 32 bits') {
           gitlabCommitStatus("Compiling linux 32 bits") {
                 ...
                }        
        }        

        
        stage('Compiling win32') {
            gitlabCommitStatus("Compiling win32") {
              ...
                }
        }
 
 
        stage('Deploy') {
            gitlabCommitStatus("Deploy") {
             ...    
        }
       }
   
    }
         currentBuild.result = 'SUCCESS'

    } // try
    catch(all) {
        echo "Il y a eu des erreurs"
        currentBuild.result = 'FAILURE'
        notifyFailed()
    }
    finally {
     // Si le build passe de failure a normal 
        if (currentBuild.getPreviousBuild().result == 'FAILURE') {
         if (currentBuild.result == 'SUCCESS') {
                echo 'build has been fixed'
                notifyFixed()
            }
        }
    } 
    echo "RESULT: ${currentBuild.result}"

}

def notifyFixed()
{
    emailext (
            subject:"[Integration Continue] ${env.JOB_NAME} - Compilation # ${env.BUILD_NUMBER} - Build has been fixed",
            body:"""
            <p>Compilation fixed par commit ${env.GIT_COMMIT}

            "<a href="${env.BUILD_URL}">${env.JOB_NAME} [${env.BUILD_NUMBER}]</a>"
            </p>
            """,
            recipientProviders:[[$class: 'DevelopersRecipientProvider'],[$class: 'CulpritsRecipientProvider']]
            )

}

def notifyFailed() {
    emailext (
            subject:"[Integration Continue] ${env.JOB_NAME} - Compilation # ${env.BUILD_NUMBER} - FAILED:",
            body:"""
            <p>
            Commit ${env.GIT_COMMIT} 
            Vérifier la sortie de la console pour voir le résultat de la compilation :
            "<a href="${env.BUILD_URL}">${env.JOB_NAME} [${env.BUILD_NUMBER}]</a>"
            </p>
            """,
            recipientProviders:[[$class: 'DevelopersRecipientProvider'],[$class: 'CulpritsRecipientProvider']]
            )
}