blocks|key|4335490|text|就像@mkobit所说的，你可以在流水线块之外将变量定义到全局级别。你试过吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4335491|def+my_var
pipeline+{
++++agent+any
++++stages+{
++++++++stage('Example')+{
++++++++++++steps+{
++++++++++++++++my_var+=+'value1'
++++++++++++}
++++++++}

++++++++stage('Example2')+{
++++++++++++steps+{
++++++++++++++++printl(my_var)
++++++++++++}
++++++++}

++++}
}|code-block|syntax|javascript|4335492|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|$]]

Like @mkobit says, you can define the variable to global level out of pipeline block. Have you tried that?

<pre><code>def my_var
pipeline {
 agent any
 stages {
 stage('Example') {
 steps {
 my_var = 'value1'
 }
 }

 stage('Example2') {
 steps {
 printl(my_var)
 }
 }

 }
}
</code></pre>

blocks|key|4335236|text|这是没有错误的工作，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4335237|def+my_var
pipeline+{
++++agent+any
++++environment+{
++++++++REVISION+=+""
++++}
++++stages+{
++++++++stage('Example')+{
++++++++++++steps+{
++++++++++++++++script{
++++++++++++++++++++my_var+=+'value1'
++++++++++++++++}
++++++++++++}
++++++++}

++++++++stage('Example2')+{
++++++++++++steps+{
++++++++++++++++script{
++++++++++++++++++++echo+"$my_var"+
++++++++++++++++}
++++++++++++}
++++++++}
++++}
}|code-block|syntax|javascript|4335238|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|$]]

This is working without an error,
<pre><code>def my_var
pipeline {
 agent any
 environment {
 REVISION = &quot;&quot;
 }
 stages {
 stage('Example') {
 steps {
 script{
 my_var = 'value1'
 }
 }
 }

 stage('Example2') {
 steps {
 script{
 echo &quot;$my_var&quot; 
 }
 }
 }
 }
}
</code></pre>

blocks|key|4335283|text|对于字符串，将其添加到'environment‘块中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4335284|pipeline+{
++environment+{
++++myGlobalValue+=+'foo'
++}
}|code-block|syntax|javascript|4335285|但对于非字符串变量，我找到的声明性管道最简单的解决方案是将值包装在一个方法中。|4335286|示例：|4335287|pipeline+{
++//+Now+I+can+reference+myGlobalValue()+in+my+pipeline.
++...
}

def+myGlobalValue()+{
++++return+['A',+'list',+'of',+'values']

//+I+can+also+reference+myGlobalValue()+in+other+methods+below
def+myGlobalSet()+{
++++return+myGlobalValue().toSet()
}|4335288|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

For strings, add it to the 'environment' block:

<pre><code>pipeline {
 environment {
 myGlobalValue = 'foo'
 }
}
</code></pre>

But for non-string variables, the easiest solution I've found for declarative pipelines is to wrap the values in a method.

Example:

<pre><code>pipeline {
 // Now I can reference myGlobalValue() in my pipeline.
 ...
}

def myGlobalValue() {
 return ['A', 'list', 'of', 'values']

// I can also reference myGlobalValue() in other methods below
def myGlobalSet() {
 return myGlobalValue().toSet()
}
</code></pre>

blocks|key|4335570|text|这对我很有效|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4335571|pipeline+{
++++agent+any
++++stages+{
++++++++stage('Example')+{
++++++++++++steps+{
+++++++++++++++script{
++++++++++++++++++env.my_var+=+'value1'
+++++++++++++++}
++++++++++++}
++++++++}

++++++++stage('Example2')+{
++++++++++++steps+{
++++++++++++++++printl(my_var)
++++++++++++}
++++++++}

++++}
}|code-block|syntax|javascript|4335572|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|$]]

This worked for me

<pre><code>pipeline {
 agent any
 stages {
 stage('Example') {
 steps {
 script{
 env.my_var = 'value1'
 }
 }
 }

 stage('Example2') {
 steps {
 printl(my_var)
 }
 }

 }
}
</code></pre>

Previously <a href="https://stackoverflow.com/questions/47684675/define-global-environment-variables-from-inside-a-stage">asked a question</a> about how to overwrite variables defined in an environment directive and it seems that's not possible.

I want to set a variable in one stage and have it accessible to other stages.
In a declarative pipeline it seems the only way to do this is in a script{} block.

For example I need to set some vars after checkout. So at the end of the checkout stage I have a script{} block that sets those vars and they are accessible in other stages.

This works, but it feels wrong. And for the sake of readability I'd much prefer to declare these variables at the top of the pipeline and have them overwritten. So that would mean having a "set variables" stage at the beginning with a script{} block that just defines vars- thats ugly.

I'm pretty sure I'm missing an obvious feature here. Do declarative pipelines have a global variable feature or must I use script{}

How do you handle global variables in a declarative pipeline?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

以前，关于如何重写环境指令中定义的变量的似乎是不可能的。我想在一个阶段中设置一个变量，并让其他阶段可以访问它。在声明式管道中，似乎唯一的方法是在script{}块中完成此操作。例如，我需要在结帐后设置一些变量。因此，在结帐阶段结束时，我有一个脚本{}块来设置这些变量，它们可以在其他阶段中访问。这行得通，但感觉不对。出于...

问如何在声明性管道中处理全局变量？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在声明性管道中处理全局变量？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在声明性管道中处理全局变量？
EN