在声明性Jenkinsfile的列表中设置变量

时间:2020-08-18 14:32:35

标签: jenkins-pipeline jenkins-groovy jenkins-declarative-pipeline

我设置了一些环境变量,如下所示:

environment {
      IMG_TARGET = "registry/cloud-environemnt-azu:1.x.x"
      CREDENTIALS = 'credentials-token'
      BUILD_DIR = 'Builddir'
      DOMAIN_DIR = 'Domaindir'
      BUILD_SOLUTION = 'Dir.Builddir.sln'
   }

Jenkins管道中使用了一些变量,我希望将它们与环境变量分开,以便仅凭据和映像目标位于环境变量中。

有没有一种方法可以使用全局列表/变量/映射来存储非环境变量,例如:

List<String> variables = [
      BUILD_DIR = 'Builddir'
      DOMAIN_DIR = 'Domaindir'
      BUILD_SOLUTION = 'Dir.Builddir.sln'
   ]

如果是这样,如何从该列表中引用变量?在管道的多个阶段中都引用了变量

2 个答案:

答案 0 :(得分:0)

您可以为您的管道提供一个环境部分,如果需要,可以在每个阶段中定义一个新的环境部分,以覆盖现有变量或定义新变量。 Example

pipeline {
    agent any

    environment {
        FOO = "bar"
        NAME = "Joe"
    }

    stages {
        stage("Env Variables") {
            environment {
                NAME = "Alan" // overrides pipeline level NAME env variable
                BUILD_NUMBER = "2" // overrides the default BUILD_NUMBER
            }

            steps {
                echo "FOO = ${env.FOO}" // prints "FOO = bar"
                echo "NAME = ${env.NAME}" // prints "NAME = Alan"
                echo "BUILD_NUMBER =  ${env.BUILD_NUMBER}" // prints "BUILD_NUMBER = 2"

                script {
                    env.SOMETHING = "1" // creates env.SOMETHING variable
                }
            }
        }

        stage("Override Variables") {
            steps {
                script {
                    env.FOO = "IT DOES NOT WORK!" // it can't override env.FOO declared at the pipeline (or stage) level
                    env.SOMETHING = "2" // it can override env variable created imperatively
                }

                echo "FOO = ${env.FOO}" // prints "FOO = bar"
                echo "SOMETHING = ${env.SOMETHING}" // prints "SOMETHING = 2"

                withEnv(["FOO=foobar"]) { // it can override any env variable
                    echo "FOO = ${env.FOO}" // prints "FOO = foobar"
                }

                withEnv(["BUILD_NUMBER=1"]) {
                    echo "BUILD_NUMBER = ${env.BUILD_NUMBER}" // prints "BUILD_NUMBER = 1"
                }
            }
        }
    }
}
 

另一种选择是在声明式管道中使用参数化的作业,如果您有兴趣,可以阅读更多here

答案 1 :(得分:0)

您可以通过在以下阶段中包含环境块来设置特定于每个阶段的环境变量。

pipeline {
    agent any
    stages {
        stage ("Test Stage"){
           environment {
              TEST_VARIABLE=test
           }
           steps {
             echo "Hello"
           }
        }
    }
}

如果要将所有非环境变量合并为单个组件,则可以使用map而不是List,因为map将数据存储在键值对中,并且您可以在任何时间点检索任何键,而使用List不能存储值作为键值对。

pipeline {
    agent any
    stages {
        stage ("Test Stage"){
            steps {
                script {
                    def testMap = [BUILD_DIR:'Builddir',DOMAIN_DIR:'Domaindir',BUILD_SOLUTION:'Dir.Builddir.sln']
                    testMap.each {
                        entry -> echo "${entry.key}"
                    }
                    echo "${testMap['DOMAIN_DIR']}"
                }
            }
        }
    }
}

谢谢

相关问题