blocks|key|4422980|text|我就想明白了。管道作业公开了一个具有可写属性的currentBuild全局变量。可以使用以下命令设置描述：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4422981|currentBuild.description+=+"my+new+description"|code-block|syntax|javascript|4422982|管道脚本中的任何位置。有关详细信息，请参阅此DZone+tutorial。|4422983|entityMap|0|LINK|mutability|MUTABLE|url|https://dzone.com/refcardz/continuous-delivery-with-jenkins-workflow^0|N|C|0|0|M|E|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Just figured it out. The pipeline job exposes a <code>currentBuild</code> global variable with writable properties. Setting the description can be done with:

<pre><code>currentBuild.description = "my new description"
</code></pre>

anywhere in the pipeline script. More information in this <a href="https://dzone.com/refcardz/continuous-delivery-with-jenkins-workflow" rel="noreferrer">DZone tutorial</a>.

blocks|key|4422817|text|@jjst的回答描述了如何在“脚本化管道”中设置构建描述。在声明性管道中，您也可以这样做，但需要将其放在script+{+}块中。下面是取自comments+on+a+Cloudbees+article的一个完整的工作示例|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4422818|pipeline+{
++++agent+any
++++stages+{
++++++++stage("1st+stage")+{
++++++++++++steps+{
++++++++++++++++script+{
++++++++++++++++++++currentBuild.displayName+=+"My+custom+build+name"
++++++++++++++++++++currentBuild.description+=+"My+custom+build+description"
++++++++++++++++}
++++++++++++}
++++++++}
++++}
}|code-block|syntax|javascript|4422819|entityMap|0|LINK|mutability|MUTABLE|url|https://support.cloudbees.com/hc/en-us/articles/220860347/comments/360000490231^0|1G|A|1Y|V|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

The answer from @jjst describes how to set the build description in &quot;scripted pipelines&quot;. In declarative pipelines you can do the same, but need to place it inside a <code>script { }</code> block. Here a complete working example taken from <a href="https://support.cloudbees.com/hc/en-us/articles/220860347/comments/360000490231" rel="nofollow noreferrer">comments on a Cloudbees article</a>:
<pre><code>pipeline {
 agent any
 stages {
 stage(&quot;1st stage&quot;) {
 steps {
 script {
 currentBuild.displayName = &quot;My custom build name&quot;
 currentBuild.description = &quot;My custom build description&quot;
 }
 }
 }
 }
}
</code></pre>

blocks|key|4423054|text|当jjst写下他的答案时，情况可能并非如此，但现在有了最新的jenkins和插件，您可以将其设置在主管道之外的顶部。这意味着你不必嵌入脚本设置和有特殊的步骤等，例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4423055|currentBuild.description+=+"my+new+description"
pipeline+{...|code-block|syntax|javascript|4423056|或|4423057|currentBuild.description+=+"""
blah
blah
blah
"""
pipeline+{|4423058|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

This may not have been the case when jjst wrote his answer but now with the latest jenkins and plugins you can set this outside the main pipeline at the top. This means you dont have to embed script setting and have special steps etc eg

<pre><code>currentBuild.description = "my new description"
pipeline {...
</code></pre>

or

<pre><code>currentBuild.description = """
blah
blah
blah
"""
pipeline {
</code></pre>

blocks|key|4423109|text|我不确定它有多老，但我最近发现了一个buildDescription插件，它为您提供了一个声明性方法来设置构建描述。安装后，它就像下面这样简单：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4423110|steps+{
++buildDescription+'my+build'
}|code-block|syntax|javascript|4423111|控制台将显示步骤输出：New+run+description+is+'my+build'|4423112|entityMap^0|I|G|0|0|B|X|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

I'm not sure how old it is, but I recently discovered the <code>buildDescription</code> plugin that gives you a declarative method to set the build description. 
Once installed, it's as easy as:

<pre><code>steps {
 buildDescription 'my build'
}
</code></pre>

The console will show a step output:
<code>New run description is 'my build'</code>

I'm trying to replace our current build pipeline, currently hacked together using old-school Jenkins jobs, with a new job that uses the Jenkins pipeline plugin, and loads a <code>Jenkinsfile</code> from the project repository.

One thing that the legacy job did was set the build description to include the Mercurial hash, username and current version using the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Project+Description+Setter+Plugin" rel="noreferrer">Description setter plugin</a>, so that builds are easy to find.

Is there a way to replicate/emulate this behaviour with the Jenkins pipeline plugin?

Jenkins pipeline plugin: set the build description

我正在尝试用一个使用Jenkins管道插件并从项目存储库加载Jenkinsfile的新作业来替换我们当前的构建管道，目前使用的是老式Jenkins作业。遗留作业所做的一件事是设置构建描述，以包括Mercurial哈希、用户名和使用的当前版本，以便很容易找到构建。有没有办法用Jenkins管道插件复制/模拟这种行为？

问Jenkins pipeline插件:设置构建描述
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins pipeline插件:设置构建描述EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins pipeline插件:设置构建描述
EN