bash – 无法在Jenkins管道作业中通过DSL(groovy)存储sh命令输出

前端之家收集整理的这篇文章主要介绍了bash – 无法在Jenkins管道作业中通过DSL(groovy)存储sh命令输出前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我想在管道Jenkins作业中获得最后的构建输出并附加在电子邮件中(使用emailext插件). Curl工作正常,并提供正确的构建输出,但我不能存储在变量中以附加在电子邮件中.我正在使用最新的jenkins版本.

我可以看到有几个简单的sh命令的相关帖子,但这对curl响应存储不起作用.

试过的代码

1.

  1. def consoleOutput = sh(returnStdout: true,script: 'curl http://' + jenkinsUser + ':' + jenkinsUserToken + '@' + jenkinsServer + ':8080/job/' + 'myJob/lastBuild/consoleText').trim()
  2. echo consoleOutput

2.

  1. sh 'curl http://' + jenkinsUser + ':' + jenkinsUserToken + '@' + jenkinsServer + ':8080/job/' + "${env.JOB_NAME}" + '/lastBuild/consoleText; echo $? > status'
  2. def consoleOutput = readFile('status').trim()

3.

  1. def consoleOutput = sh(script: 'curl http://' + jenkinsUser + ':' + jenkinsUserToken + '@' + jenkinsServer + ':8080/job/' + '/myJob/lastBuild/consoleText',returnStatus: true).split("\r?\n")
  2. echo consoleOutput
看起来你错过了内部数组和一些双引号并转义了双引号来运行脚本:
  1. sh([ script: "curl \"http://${jenkinsUser}:${jenkinsUserToken}@${jenkinsServer}:8080/job/myJob/lastBuild/consoleText\"").trim()

还有多种方法可以执行shell脚本,这取决于您使用的jenkins管道的类型.

jenkins declarative pipeline中,您需要为所有脚本类型代码和设置变量包含一个脚本{…}块,如下所示:

  1. pipeline {
  2. agent {
  3. ...
  4. }
  5. parameters {
  6. ...
  7. }
  8. environment {
  9. ...
  10. }
  11. stages {
  12. stage('Run required Scripts') {
  13. steps {
  14. ...
  15. script {
  16. NOTIFIER_BULD_NAME = sh([script: "./getNotifier.sh",returnStdout: true]).trim()
  17. EMAIL_TEXT = sh([script: "./printEmailText.sh ${CURRENT_BUILD} ${PREVIoUS_BUILD}",returnStdout: true]).trim()
  18. BODY= sh([ script: "curl \"http://${jenkinsUser}:${jenkinsUserToken}@${jenkinsServer}:8080/job/myJob/lastBuild/consoleText\"").trim()
  19. }
  20. }
  21. }
  22. stage('Send Email') {
  23. when {
  24. expression {
  25. // Only send when there is text.
  26. "${EMAIL_TEXT}" != "";
  27. }
  28. }
  29. steps{
  30. emailext (
  31. to: 'software@company.com',subject: "You have mail - ${EMAIL_TEXT}",body: """${NOTIFIER_BULD_NAME} - ${EMAIL_TEXT}:
  32. ...
  33. ${BODY}
  34. """,attachLog: false
  35. )
  36. }
  37. }
  38. }

Jenkins scripted pipeline中,您不需要脚本{}块,实际上可以将它放在大多数地方.大多数情况下,我把它放在舞台块阶段(‘某个舞台’){…},我这样做了:

  1. V5_DIR = WORKSPACE + '/' + sh([script: "basename ${V5_GIT_URL} .git",returnStdout: true]).trim()

虽然我也使用curl命令(对于脚本管道)并且不需要内部数组…

  1. lastSuccessfulCommit = sh(
  2. script: "curl -sL --user ${JENKINS_API_USER}:${JENKINS_API_PSW} \"${lastSuccessfulCommitUrl}\" | sed -e 's/<[^>]*>//g'",returnStdout: true
  3. )

作为参考,回声变量在两者中都是这样的

  1. sh([script: "echo \"Value: ${someVariable}\""])

希望this documentation有点帮助,但我知道最近jenkins的文档可能非常参差不齐,所以我也找到了a great gist about how to not do things for Jenkins Declarative pipelines.祝你好运!

猜你在找的Bash相关文章