问题描述
我想以某种方式将我在阶段 A 中读取的变量传递给阶段 B.我在一些示例中看到人们将其写入文件，但我想这并不是一个很好的解决方案.我尝试将它写入环境变量，但我并没有真正成功.如何正确设置?
I want to pass a variable which I read in stage A towards stage B somehow. I see in some examples that people write it to a file, but I guess that is not really a nice solution. I tried writing it to an environment variable, but I'm not really successful on that. How can I set it up properly?
为了让它工作，我尝试了很多东西并读到我应该使用 """ 而不是 ''' 来启动一个 shell 并将这些变量转义到 ${foo}例子.
To get it working I tried a lot of things and read that I should use the """ instead of ''' to start a shell and escape those variables to ${foo} for example.
以下是我所拥有的管道:
Below is what I have as a pipeline:
#!/usr/bin/env groovy
pipeline {
agent { node { label 'php71' } }
environment {
packageName='my-package'
packageVersion=''
groupId='vznl'
nexus_endpoint='http://nexus.devtools.io'
nexus_username='jenkins'
nexus_password='J3nkins'
}
stages{
// Package dependencies
stage('Install dependencies') {
steps {
sh '''
echo Skip composer installation
#composer install --prefer-dist --optimize-autoloader --no-interaction
'''
}
}
// Unit tests
stage('Unit Tests') {
steps {
sh '''
echo Running PHP code coverage tests...
#composer test
'''
}
}
// Create artifact
stage('Package') {
steps {
echo 'Create package refs'
sh """
mkdir -p ./build/zpk
VERSIONTAG=$(grep 'version' composer.json)
REGEX='"version": "([0-9]+.[0-9]+.[0-9]+)"'
if [[ ${VERSIONTAG} =~ ${REGEX} ]]
then
env.packageVersion=${BASH_REMATCH[1]}
/usr/bin/zs-client packZpk --folder=. --destination=./build/zpk --name=${env.packageName}-${env.packageVersion}.zpk --version=${env.packageVersion}
else
echo "No version found!"
exit 1
fi
"""
}
}
// Publish ZPK package to Nexus
stage('Publish packages') {
steps {
echo "Publish ZPK Package"
sh "curl -u ${env.nexus_username}:${env.nexus_password} --upload-file ./build/zpk/${env.packageName}-${env.packageVersion}.zpk ${env.nexus_endpoint}/repository/zpk-packages/${groupId}/${env.packageName}-${env.packageVersion}.zpk"
archive includes: './build/**/*.{zpk,rpm,deb}'
}
}
}
}
如您所见，我从阶段 Package 中读取的 packageVersion 也需要在阶段 Publish 中使用.
As you can see the packageVersion which I read from stage Package needs to be used in stage Publish as well.
当然也欢迎针对管道的总体提示.
Overall tips against the pipeline are of course always welcome as well.
推荐答案
您的代码中的一个问题是您在 sh 步骤中分配了环境变量的版本.这一步会在自己的独立进程中执行，继承父进程环境变量.
A problem in your code is that you are assigning version of environment variable within the sh step. This step will execute in its own isolated process, inheriting parent process environment variables.
但是，将数据传回父级的唯一方法是通过 STDOUT/STDERR 或退出代码.如果您想要一个字符串值，最好从 sh 步骤中回显版本并将其分配给 script 上下文中的变量.
However, the only way of passing data back to the parent is through STDOUT/STDERR or exit code. As you want a string value, it is best to echo version from the sh step and assign it to a variable within the script context.
如果你重用节点，脚本上下文将保持不变，变量将在后续阶段可用.下面是一个工作示例.请注意，任何将其放在 parallel 块中的尝试都可能失败，因为版本信息变量可以被多个进程写入.
If you reuse the node, the script context will persist, and variables will be available in the subsequent stage. A working example is below. Note that any try to put this within a parallel block can be of failure, as the version information variable can be written to by multiple processes.
#!/usr/bin/env groovy
pipeline {
environment {
AGENT_INFO = ''
}
agent {
docker {
image 'alpine'
reuseNode true
}
}
stages {
stage('Collect agent info'){
steps {
echo "Current agent info: ${env.AGENT_INFO}"
script {
def agentInfo = sh script:'uname -a', returnStdout: true
println "Agent info within script: ${agentInfo}"
AGENT_INFO = agentInfo.replace("/n", "")
env.AGENT_INFO = AGENT_INFO
}
}
}
stage("Print agent info"){
steps {
script {
echo "Collected agent info: ${AGENT_INFO}"
echo "Environment agent info: ${env.AGENT_INFO}"
}
}
}
}
}
这篇关于在 Jenkins 阶段之间传递变量的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，WP2