blocks|key|2170746|text|使用文本查找器插件。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2170747|不要退出状态1(这将导致生成失败)，请执行：|2170748|if+($build_error)+print("TESTS+FAILED!");|code-block|syntax|javascript|2170749|在构建后的操作中，启用文本查找器，设置正则表达式以匹配您打印的消息(TESTS+FAILED!)，并选中该条目下的“不稳定的如果找到”复选框。|style|CODE|2170750|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.jenkins-ci.org/display/JENKINS/Text-finder%2BPlugin^0|2|5|0|0|0|0|Y|D|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|12|8|@$A|13|B|14|M|N]]|9|@]|C|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Use the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Text-finder+Plugin">Text-finder</a> plugin.

Instead of exiting with status 1 (which would fail the build), do:

<pre><code>if ($build_error) print("TESTS FAILED!");
</code></pre>

Than in the post-build actions enable the Text Finder, set the regular expression to match the message you printed (<code>TESTS FAILED!</code>) and check the "Unstable if found" checkbox under that entry.

blocks|key|2170831|text|它可以不打印魔术字符串和使用TextFinder。下面是关于它的一些信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2170832|基本上，您需要一个来自.jar脚本中可用的/cli文件，然后可以使用以下命令来标记一个不稳定的构建：|2170833|java+-jar+jenkins-cli.jar+set-build-result+unstable|code-block|syntax|javascript|2170834|若要在错误上标记生成不稳定，可以使用：|2170835|failing_cmd+cmd_args+%7C%7C+java+-jar+jenkins-cli.jar+set-build-result+unstable|2170836|问题是jenkins-cli.jar必须从shell脚本中获得。您可以将其放在易于访问的路径中，也可以通过job的shell脚本下载：|2170837|wget+${JENKINS_URL}jnlpJars/jenkins-cli.jar|2170838|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.jenkins-ci.org/display/JENKINS/Jenkins%2BCLI|1|http://_yourserver.com_/cli^0|P|3|0|0|L|4|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|F|3|G|5|H|7|1A|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1C|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|1D|8|@]|9|@]|C|$]]|$1|Q|3|R|5|H|7|1E|8|@]|9|@]|C|$I|J]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]]]

It can be done without printing magic strings and using TextFinder. <a href="https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI" rel="noreferrer">Here's</a> some info on it.

Basically you need a .jar file from http://yourserver.com/cli available in shell scripts, then you can use the following command to mark a build unstable:

<pre><code>java -jar jenkins-cli.jar set-build-result unstable
</code></pre>

To mark build unstable on error, you can use:

<pre><code>failing_cmd cmd_args || java -jar jenkins-cli.jar set-build-result unstable
</code></pre>

The problem is that jenkins-cli.jar has to be available from shell script. You can either put it in easy-to-access path, or download in via job's shell script:

<pre><code>wget ${JENKINS_URL}jnlpJars/jenkins-cli.jar
</code></pre>

blocks|key|348690|text|您还应该能够使用groovy并执行textfinder所做的工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348691|使用groovy后构建插件将构建标记为不稳定的|offset|length|348692|if(manager.logContains("Could+not+login+to+FTP+server"))+{
++++manager.addWarningBadge("FTP+Login+Failure")
++++manager.createSummary("warning.gif").appendText("<h1>Failed+to+login+to+remote+FTP+Server!</h1>",+false,+false,+false,+"red")
++++manager.buildUnstable()
}|code-block|syntax|javascript|348693|还请参见Groovy+Postbuild插件|348694|entityMap|0|LINK|mutability|MUTABLE|url|http://jenkins.361315.n4.nabble.com/marking-a-build-as-un-stable-with-groovy-post-build-plugin-td4637798.html|1|https://wiki.jenkins-ci.org/display/JENKINS/Groovy%2BPostbuild%2BPlugin^0|0|0|N|0|0|0|4|I|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]]]

you should also be able to use groovy and do what textfinder did

<a href="http://jenkins.361315.n4.nabble.com/marking-a-build-as-un-stable-with-groovy-post-build-plugin-td4637798.html" rel="noreferrer">marking a build as un-stable with groovy post-build plugin</a>

<pre><code>if(manager.logContains("Could not login to FTP server")) {
 manager.addWarningBadge("FTP Login Failure")
 manager.createSummary("warning.gif").appendText("&lt;h1&gt;Failed to login to remote FTP Server!&lt;/h1&gt;", false, false, false, "red")
 manager.buildUnstable()
}
</code></pre>

Also see <a href="https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin" rel="noreferrer">Groovy Postbuild Plugin</a>

blocks|key|161041|text|您只需调用“退出1"，构建就会在此时失败，而不会继续。最后，我创建了一个传递函数来为我处理它，并调用safemake而不是make用于构建：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161042|function+safemake+{
++make+"$@"
++if+[+"$?"+-ne+0+];+then
++++echo+"ERROR:+BUILD+FAILED"
++++exit+1
++else
++++echo+"BUILD+SUCCEEDED"
++fi
}|code-block|syntax|javascript|161043|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can just call "exit 1", and the build will fail at that point and not continue. I wound up making a passthrough make function to handle it for me, and call safemake instead of make for building:

<pre><code>function safemake {
 make "$@"
 if [ "$?" -ne 0 ]; then
 echo "ERROR: BUILD FAILED"
 exit 1
 else
 echo "BUILD SUCCEEDED"
 fi
}
</code></pre>

blocks|key|348732|text|在我的作业脚本中，我有以下语句(此作业仅在Jenkins主服务器上运行)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348733|#+This+is+the+condition+test+I+use+to+set+the+build+status+as+UNSTABLE
if+[+${PERCENTAGE}+-gt+80+-a+${PERCENTAGE}+-lt+90+];+then
++echo+WARNING:+disc+usage+percentage+above+80%25

++#+Download+the+Jenkins+CLI+JAR:
++curl+-o+jenkins-cli.jar+${JENKINS_URL}/jnlpJars/jenkins-cli.jar

++#+Set+build+status+to+unstable
++java+-jar+jenkins-cli.jar+-s+${JENKINS_URL}/+set-build-result+unstable

fi|code-block|syntax|javascript|348734|您可以看到这一点和关于在Jenkins：https://wiki.jenkins-ci.org/display/JENKINS/Jenkins%2BCLI上设置构建状态的更多信息。|offset|length|348735|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.jenkins-ci.org/display/JENKINS/Jenkins%2BCLI^0|0|0|K|1J|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

In my job script, I have the following statements (this job only runs on the Jenkins master):

<pre><code># This is the condition test I use to set the build status as UNSTABLE
if [ ${PERCENTAGE} -gt 80 -a ${PERCENTAGE} -lt 90 ]; then
 echo WARNING: disc usage percentage above 80%

 # Download the Jenkins CLI JAR:
 curl -o jenkins-cli.jar ${JENKINS_URL}/jnlpJars/jenkins-cli.jar

 # Set build status to unstable
 java -jar jenkins-cli.jar -s ${JENKINS_URL}/ set-build-result unstable

fi
</code></pre>

You can see this and a lot more information about setting build statuses on the Jenkins wiki: <a href="https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI" rel="noreferrer">https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI</a>

blocks|key|160604|text|配置PHP以生成xml报告
……|type|ordered-list-item|depth|inlineStyleRanges|entityRanges|data|160605|完成状态为0的构建脚本
..。0出口；|160606|添加构建后操作发布JUnit测试结果报告用于测试报告XML。当测试失败时，这个插件会将稳定的构建变成不稳定的。
**/build/junit.xml|offset|length|style|BOLD|160607|添加带有控制台输出、扫描和未选中选项的Jenkins文本查找器插件。这个插件在致命错误的基础上失败了。
PHP致命错误：|160608|unstyled|entityMap^0|0|0|7|D|0|J|C|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@$F|R|G|S|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|T|8|@$F|U|G|V|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|M|7|W|8|@]|9|@]|A|$]]]|N|$]]

<ol>
<li>Configure PHP build to produce xml junit report

<pre><code>&lt;phpunit bootstrap="tests/bootstrap.php" colors="true" &gt;
 &lt;logging&gt;
 &lt;log type="junit" target="build/junit.xml" 
 logIncompleteSkipped="false" title="Test Results"/&gt;
 &lt;/logging&gt;

 ....

 &lt;/phpunit&gt;
</code></pre></li>
<li>Finish build script with status 0

<pre><code>...
exit 0;
</code></pre></li>
<li>Add post-build action Publish JUnit test result report for Test report XMLs. This plugin will change Stable build to Unstable when test are failing. 

<pre><code>**/build/junit.xml
</code></pre></li>
<li>Add Jenkins Text Finder plugin with console output scanning and unchecked options. This plugin fail whole build on fatal error.

<pre><code>PHP Fatal error:
</code></pre></li>
</ol>

blocks|key|160623|text|我发现最灵活的方法是在groovy+post构建插件中读取一个文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|160624|📷|atomic|offset|length|160625|​|160626|import+hudson.FilePath
import+java.io.InputStream

def+build+=+Thread.currentThread().executable

String+unstable+=+null
if(build.workspace.isRemote())+{
++++channel+=+build.workspace.channel;
++++fp+=+new+FilePath(channel,+build.workspace.toString()+%2B+"/build.properties")
++++InputStream+is+=+fp.read()
++++unstable+=+is.text.trim()
}+else+{
++++fp+=+new+FilePath(new+File(build.workspace.toString()+%2B+"/build.properties"))
++++InputStream+is+=+fp.read()
++++unstable+=+is.text.trim()
}

manager.listener.logger.println("Build+status+file:+"+%2B+unstable)
if+(unstable.equalsIgnoreCase('true'))+{
++++manager.listener.logger.println('setting+build+to+unstable')
++++manager.buildUnstable()
}|code-block|syntax|javascript|160627|如果文件内容为“true”，则构建将设置为不稳定。这将适用于本地主机和运行作业的任何奴隶，以及可以写入磁盘的任何类型的脚本。|160628|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/a2f54bb65eeb2096f4c37f6e82522f8d.png|imageAlt^0|0|0|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@$E|10|F|11|1|12]]|A|$]]|$1|G|3|H|5|6|7|13|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|14|8|@]|9|@]|A|$L|M]]|$1|N|3|O|5|6|7|15|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W|X|-4]]]]

I find the most flexible way to do this is by reading a file in the groovy post build plugin.
<a href="https://i.stack.imgur.com/YEK0u.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/YEK0u.png" alt="enter image description here"></a>

<pre><code>import hudson.FilePath
import java.io.InputStream

def build = Thread.currentThread().executable

String unstable = null
if(build.workspace.isRemote()) {
 channel = build.workspace.channel;
 fp = new FilePath(channel, build.workspace.toString() + "/build.properties")
 InputStream is = fp.read()
 unstable = is.text.trim()
} else {
 fp = new FilePath(new File(build.workspace.toString() + "/build.properties"))
 InputStream is = fp.read()
 unstable = is.text.trim()
}

manager.listener.logger.println("Build status file: " + unstable)
if (unstable.equalsIgnoreCase('true')) {
 manager.listener.logger.println('setting build to unstable')
 manager.buildUnstable()
}
</code></pre>

If the file contents are 'true' the build will be set to unstable. This will work on the local master and on any slaves you run the job on, and for any kind of scripts that can write to disk.

blocks|key|161108|text|只有当作业状态没有从成功更改为失败或中止时，TextFinder才是好的。对于这种情况，在PostBuild步骤中使用groovy脚本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161109|errpattern+=+~/TEXT-TO-LOOK-FOR-IN-JENKINS-BUILD-OUTPUT.*/;
manager.build.logFile.eachLine{+line+->
++++errmatcher=errpattern.matcher(line)
++++if+(errmatcher.find())+{
++++++++manager.build.@result+=+hudson.model.Result.NEW-STATUS-TO-SET
++++}
+}|code-block|syntax|javascript|161110|在我写过的一篇文章中可以看到更多的细节：http://www.tikalk.com/devops/JenkinsJobStatusChange/|offset|length|161111|entityMap|0|LINK|mutability|MUTABLE|url|http://www.tikalk.com/devops/JenkinsJobStatusChange/^0|0|0|K|1G|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

The TextFinder is good only if the job status hasn't been changed from SUCCESS to FAILED or ABORTED.
For such cases, use a groovy script in the PostBuild step:

<pre><code>errpattern = ~/TEXT-TO-LOOK-FOR-IN-JENKINS-BUILD-OUTPUT.*/;
manager.build.logFile.eachLine{ line -&gt;
 errmatcher=errpattern.matcher(line)
 if (errmatcher.find()) {
 manager.build.@result = hudson.model.Result.NEW-STATUS-TO-SET
 }
 }
</code></pre>

See more details in a post I've wrote about it:
<a href="http://www.tikalk.com/devops/JenkinsJobStatusChange/" rel="nofollow">http://www.tikalk.com/devops/JenkinsJobStatusChange/</a>

blocks|key|348824|text|复制了https://stackoverflow.com/a/47158087/2799191的答案，因为我花了一些时间寻找以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|348825|在Jenkins的较新版本中，现在可以这样做：|348826|#!/usr/bin/env+groovy

properties([
++parameters([string(name:+'foo',+defaultValue:+'bar',+description:+'Fails+job+if+not+bar+(unstable+if+bar)')]),
])


stage('Stage+1')+{
++node('parent'){
++++def+ret+=+sh(
++++++returnStatus:+true,+//+This+is+the+key+bit!
++++++script:+'''if+[+"$foo"+=+bar+];+then+exit+2;+else+exit+1;+fi'''
++++)
++++//+ret+can+be+any+number/range,+does+not+have+to+be+2.
++++if+(ret+==+2)+{
++++++currentBuild.result+=+'UNSTABLE'
++++}+else+if+(ret+!=+0)+{
++++++currentBuild.result+=+'FAILURE'
++++++//+If+you+do+not+manually+error+the+status+will+be+set+to+"failed",+but+the
++++++//+pipeline+will+still+run+the+next+stage.
++++++error("Stage+1+failed+with+exit+code+${ret}")
++++}
++}
}|code-block|syntax|javascript|348827|管道语法生成器在高级选项卡中显示了这一点：|348828|​|348829|📷|atomic|348830|348831|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/47158087/2799191|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/e8ed7c25357f9b6014facc341bf97733.png|imageAlt^0|3|18|0|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1B|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1C|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1D|8|@]|9|@]|C|$]]|$1|O|3|P|5|Q|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|R|3|N|5|6|7|1I|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1J|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|11|W|12|C|$13|14|15|-4]]]]

Duplicating my answer from <a href="https://stackoverflow.com/a/47158087/2799191">here</a> because I spent some time looking for this:

This is now possible in newer versions of Jenkins, you can do something like this:

<pre><code>#!/usr/bin/env groovy

properties([
 parameters([string(name: 'foo', defaultValue: 'bar', description: 'Fails job if not bar (unstable if bar)')]),
])


stage('Stage 1') {
 node('parent'){
 def ret = sh(
 returnStatus: true, // This is the key bit!
 script: '''if [ "$foo" = bar ]; then exit 2; else exit 1; fi'''
 )
 // ret can be any number/range, does not have to be 2.
 if (ret == 2) {
 currentBuild.result = 'UNSTABLE'
 } else if (ret != 0) {
 currentBuild.result = 'FAILURE'
 // If you do not manually error the status will be set to "failed", but the
 // pipeline will still run the next stage.
 error("Stage 1 failed with exit code ${ret}")
 }
 }
}
</code></pre>

The Pipeline Syntax generator shows you this in the advanced tab:

<a href="https://i.stack.imgur.com/VxoSe.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/VxoSe.png" alt="Pipeline Syntax Example"></a>

blocks|key|348857|text|我想我会发布另一个答案的人，可能是寻找类似的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348858|在我们的构建工作中，我们有希望继续构建的情况，但是被标记为不稳定。对我们来说，这与版本号有关。|348859|因此，我希望在构建上设置一个条件，如果满足该条件，则将构建设置为不稳定。|348860|我使用条件步骤(单)选项作为构建步骤。|offset|length|style|BOLD|348861|然后，我使用执行系统Groovy脚本作为在满足该条件时运行的构建步骤。|348862|我使用了Groovy命令并将脚本设置为|348863|import+hudson.model.*

def+build+=+Thread.currentThread().executable
build.@result+=+hudson.model.Result.UNSTABLE

return|code-block|syntax|javascript|348864|这似乎挺管用的。|348865|我在这里偶然发现了解决办法|348866|http://tech.akom.net/archives/112-Marking-Jenkins-build-UNSTABLE-from-environment-inject-groovy-script.html|348867|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|3|7|0|6|C|0|4|8|0|0|0|0|0|2Z|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1A|8|@$H|1B|I|1C|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1D|8|@$H|1E|I|1F|J|K]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1G|8|@$H|1H|I|1I|J|K]]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1J|8|@]|9|@]|A|$S|T]]|$1|U|3|V|5|6|7|1K|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1M|8|@]|9|@$H|1N|I|1O|1|1P]]|A|$]]|$1|10|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|Z]]]]

I thought I would post another answer for people that might be looking for something similar.

In our build job we have cases where we would want the build to continue, but be marked as unstable. For ours it's relating to version numbers.

So, I wanted to set a condition on the build and set the build to unstable if that condition is met.

I used the Conditional step (single) option as a build step.

Then I used Execute system Groovy script as the build step that would run when that condition is met.

I used Groovy Command and set the script the following

<pre><code>import hudson.model.*

def build = Thread.currentThread().executable
build.@result = hudson.model.Result.UNSTABLE

return
</code></pre>

That seems to work quite well.

I stumbled upon the solution here

<a href="http://tech.akom.net/archives/112-Marking-Jenkins-build-UNSTABLE-from-environment-inject-groovy-script.html" rel="nofollow noreferrer">http://tech.akom.net/archives/112-Marking-Jenkins-build-UNSTABLE-from-environment-inject-groovy-script.html</a>

blocks|key|348885|text|现代Jenkins版本(自2016年10月2.26以来)解决了这个问题:它只是执行shell构建步骤的一个高级选项！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348886|​|348887|📷|atomic|offset|length|348888|348889|您可以选择并设置一个任意的退出值；如果匹配，构建将是不稳定的。只需选择一个不太可能由构建中的实际过程启动的值。|348890|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/6c4c233a7126d6cbd1a30881cb9530b7.png|imageAlt^0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|I|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

Modern Jenkins versions (since 2.26, October 2016) solved this: it's just an advanced option for the Execute shell build step!

<a href="https://i.stack.imgur.com/2ZK2N.png" rel="noreferrer"><img src="https://i.stack.imgur.com/2ZK2N.png" alt="exit code for build"></a>

You can just choose and set an arbitrary exit value; if it matches, the build will be unstable. Just pick a value which is unlikely to be launched by a real process in your build.

blocks|key|2171145|text|作为现有答案的更轻松的替代方案，您可以使用一个简单的HTTP来设置构建结果，以访问Groovy脚本控制台REST+|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2171146|++++curl+-X+POST+\
+++++--silent+\
+++++--user+"$YOUR_CREDENTIALS"+\
+++++--data-urlencode+"script=Jenkins.instance.getItemByFullName(+'$JOB_NAME'+).getBuildByNumber(+$BUILD_NUMBER+).setResult(+hudson.model.Result.UNSTABLE+)"+$JENKINS_URL/scriptText|code-block|syntax|javascript|2171147|优势：|2171148|不需要下载并运行一个巨大的jar文件|unordered-list-item|2171149|没有用于设置和读取某些全局状态(控制台文本、工作区中的文件)的函数|2171150|不需要插件(除了Groovy)|2171151|不需要配置在已通过或失败情况下多余的额外构建步骤。|2171152|对于此解决方案，您的环境必须满足以下条件：|2171153|Jenkins+REST+API可以从从服务器访问。|2171154|奴隶必须能够访问允许访问Jenkins+Groovy脚本REST的凭据。|2171155|entityMap^0|Q|V|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|17|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|18|8|@]|D|@]|E|$]]|$1|P|3|Q|5|O|7|19|8|@]|D|@]|E|$]]|$1|R|3|S|5|O|7|1A|8|@]|D|@]|E|$]]|$1|T|3|U|5|O|7|1B|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|1C|8|@]|D|@]|E|$]]|$1|X|3|Y|5|O|7|1D|8|@]|D|@]|E|$]]|$1|Z|3|10|5|O|7|1E|8|@]|D|@]|E|$]]|$1|11|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|12|$]]

As a lighter alternative to the existing answers, you can set the build result with a simple HTTP POST to access the Groovy script console REST API:

<pre><code> curl -X POST \
 --silent \
 --user "$YOUR_CREDENTIALS" \
 --data-urlencode "script=Jenkins.instance.getItemByFullName( '$JOB_NAME' ).getBuildByNumber( $BUILD_NUMBER ).setResult( hudson.model.Result.UNSTABLE )" $JENKINS_URL/scriptText
</code></pre>

Advantages:

<ul>
<li>no need to download and run a huge jar file</li>
<li>no kludges for setting and reading some global state (console text, files in workspace)</li>
<li>no plugins required (besides Groovy)</li>
<li>no need to configure an extra build step that is superfluous in the PASSED or FAILURE cases.</li>
</ul>

For this solution, your environment must meet these conditions:

<ul>
<li>Jenkins REST API can be accessed from slave</li>
<li>Slave must have access to credentials that allows to access the Jenkins Groovy script REST API.</li>
</ul>

blocks|key|161189|text|将构建设置为不稳定的一个简单方法是在"execute“块中运行exit+13|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|161190|entityMap^0|V|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

One easy way to set a build as unstable, is in your &quot;execute shell&quot; block, run <code>exit 13</code>

blocks|key|160717|text|除了所有其他答案之外，jenkins还允许使用unstable()方法(在我看来，这个方法更清楚)。此方法可与描述构建不稳定的消息参数一起使用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|160718|除此之外，您还可以使用shell脚本(bat或sh)的returnStatus来启用它。|160719|例如：|160720|def+status+=+bat(script:+"<your+command+here>",+returnStatus:+true)
if+(status+!=+0)+{
++++unstable("unstable+build+because+script+failed")
}|code-block|syntax|javascript|160721|当然，您可以根据需要和返回状态来制作粒度更高的东西。|160722|此外，为了引发错误，还可以使用warnError()代替unstable()。它将指示您的构建失败而不是不稳定，但语法相同。|160723|entityMap^0|N|A|0|R|C|0|0|0|0|F|B|S|A|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|11|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|12|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|T|$]]

In addition to all others answers, jenkins also allows the use of the <code>unstable()</code> method (which is in my opinion clearer).
This method can be used with a message parameter which describe why the build is unstable.
In addition of this, you can use the <code>returnStatus</code> of your shell script (bat or sh) to enable this.
For example:
<pre><code>def status = bat(script: &quot;&lt;your command here&gt;&quot;, returnStatus: true)
if (status != 0) {
 unstable(&quot;unstable build because script failed&quot;)
}
</code></pre>
Of course, you can make something with more granularity depending on your needs and the return status.
<hr />
Furthermore, for raising error, you can also use <code>warnError()</code> in place of <code>unstable()</code>. It will indicate your build as failed instead of unstable, but the syntax is same.

blocks|key|161200|text|如果您想使用声明式方法，我建议您使用这样的代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161201|pipeline+{
++++stages+{
++++++++//+create+separate+stage+only+for+problematic+command
++++++++stage("build")+{
++++++++++++steps+{
++++++++++++++++sh+"command"
++++++++++++}
++++++++++++post+{
++++++++++++++++failure+{
++++++++++++++++++++//+set+status
++++++++++++++++++++unstable+'rsync+was+unsuccessful'
++++++++++++++++}
++++++++++++++++always+{
++++++++++++++++++++echo+"Do+something+at+the+end+of+stage"
++++++++++++++++}
++++++++++++}
++++++++}
++++}

++++post+{
++++++++always+{
++++++++++++echo+"Do+something+at+the+end+of+pipeline"
++++++++}
++++}
}|code-block|syntax|javascript|161202|如果您希望将所有内容都保持在一个阶段，请使用catchError|offset|length|style|CODE|161203|pipeline+{
++++stages+{
++++++++//+create+separate+stage+only+for+problematic+command
++++++++stage("build")+{
++++++++++++steps+{
++++++++++++++++catchError(stageResult:+'UNSTABLE')+{
++++++++++++++++++++sh+"command"
++++++++++++++++}
++++++++++++++++sh+"other+command"
++++++++++++}
++++++++}
++++}
}|161204|entityMap^0|0|0|M|A|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

If you want to use a declarative approach I suggest you to use code like this.
<pre><code>pipeline {
 stages {
 // create separate stage only for problematic command
 stage(&quot;build&quot;) {
 steps {
 sh &quot;command&quot;
 }
 post {
 failure {
 // set status
 unstable 'rsync was unsuccessful'
 }
 always {
 echo &quot;Do something at the end of stage&quot;
 }
 }
 }
 }

 post {
 always {
 echo &quot;Do something at the end of pipeline&quot;
 }
 }
}
</code></pre>
In case you want to keep everything in one stage use <code>catchError</code>
<pre><code>pipeline {
 stages {
 // create separate stage only for problematic command
 stage(&quot;build&quot;) {
 steps {
 catchError(stageResult: 'UNSTABLE') {
 sh &quot;command&quot;
 }
 sh &quot;other command&quot;
 }
 }
 }
}
</code></pre>

In a project I'm working on, we are using shell scripts to execute different tasks. Some are sh/bash scripts that run rsync, and some are PHP scripts. One of the PHP scripts is running some integration tests that output to JUnit XML, code coverage reports, and similar.

Jenkins is able to mark the jobs as successful / failed based on <a href="http://en.wikipedia.org/wiki/Exit_status" rel="noreferrer">exit status</a>. In PHP, the script exits with 1 if it has detected that the tests failed during the run. The other shell scripts run commands and use the exit codes from those to mark a build as failed.

<pre><code>// :: End of PHP script:
// If any tests have failed, fail the build
if ($build_error) exit(1);
</code></pre>

In <a href="https://wiki.jenkins-ci.org/display/JENKINS/Terminology" rel="noreferrer">Jenkins Terminology</a>, an unstable build is defined as:

<blockquote>
 A build is unstable if it was built successfully and one or more publishers report it unstable. For example if the JUnit publisher is configured and a test fails then the build will be marked unstable.
</blockquote>

How can I get Jenkins to mark a build as unstable instead of only success / failed when running shell scripts?

How to mark a build unstable in Jenkins when running shell scripts

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

在我正在处理的项目中，我们使用shell脚本来执行不同的任务。有些是运行rsync的sh/bash脚本，有些是PHP脚本。其中一个PHP脚本正在运行一些集成测试，这些测试输出到JUnit XML、代码覆盖率报告等等。Jenkins能够基于 将作业标记为成功/失败。在PHP中，如果在运行过程中检测到测试失败，脚本将以1退...

问运行shell脚本时如何在Jenkins中标记不稳定的构建
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问运行shell脚本时如何在Jenkins中标记不稳定的构建EN