Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: pipeline-model-definition-plugin
-
Labels:None
-
Similar Issues:
Description
With an environment section like this:
environment {
FOO = "something"
BAR = "${env.FOO} else"
}
The EnvVars-driven environment variable resolution/expansion doesn't know that env.FOO means that it needs to resolve FOO before resolving BAR, so there's no guarantee that'll actually happen in that order, and you may well get BAR as null else.
Attachments
Activity
Got an approach that avoids that. woot.
Hi,
I stumbled upon the same issue :
This code does not work:
withEnv([ "BUILD_TOOLS_FOLDER=${env.WORKSPACE}\\BuildTools", "PATH+NUGET=${env.BUILD_TOOLS_FOLDER}\\NuGet"]) { echo "${BUILD_TOOLS_FOLDER}" => echo c:\J\workspace\master400f232c\BuildTools echo "${PATH}" => echo null\NuGet;...PATH... }
While this code works
withEnv(["BUILD_TOOLS_FOLDER=${env.WORKSPACE}\\BuildTools"]){ withEnv(["PATH+NUGET=${env.BUILD_TOOLS_FOLDER}\\NuGet"]){ echo "${BUILD_TOOLS_FOLDER}" => echo c:\J\workspace\master400f232c\BuildTools echo "${PATH}" => echo c:\J\workspace\master400f232c\BuildTools\NuGet;...PATH... } }
Vincent Therry
added a comment - Hi,
I stumbled upon the same issue :
This code does not work:
withEnv([
"BUILD_TOOLS_FOLDER=${env.WORKSPACE}\\BuildTools" ,
"PATH+NUGET=${env.BUILD_TOOLS_FOLDER}\\NuGet" ])
{
echo "${BUILD_TOOLS_FOLDER}" => echo c:\J\workspace\master400f232c\BuildTools
echo "${PATH}" => echo null \NuGet;...PATH...
}
While this code works
withEnv([ "BUILD_TOOLS_FOLDER=${env.WORKSPACE}\\BuildTools" ]){
withEnv([ "PATH+NUGET=${env.BUILD_TOOLS_FOLDER}\\NuGet" ]){
echo "${BUILD_TOOLS_FOLDER}" => echo c:\J\workspace\master400f232c\BuildTools
echo "${PATH}" => echo c:\J\workspace\master400f232c\BuildTools\NuGet;...PATH...
}
}
What version of pipeline-model-definition do you have installed?
I have version 1.1.2 installed
All plugins are up to date
Vincent Therry
added a comment - I have version 1.1.2 installed
All plugins are up to date Ah, didn't notice that you were using withEnv. That's not a Declarative issue - open a ticket against workflow-basic-steps.
Also I noticed I cannot set environment variables like that (I work on Windows) :
environment {
PATH_TO_MY_WINDOWS_FOLDER = "C:\\MyFolder"
}
I am getting the following error :
hudson.remoting.ProxyException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
http://jenkins.eureka.lan:8080/blue/organizations/jenkins/DispatchAdminApi%2FDispatchAdminApi/detail/master/149/pipeline#log-25Script4.groovy: 1: unexpected char: '\' @ line 1, column 30.
http://jenkins.eureka.lan:8080/blue/organizations/jenkins/DispatchAdminApi%2FDispatchAdminApi/detail/master/149/pipeline#log-26 "PATH_TO_MY_WINDOWS_FOLDER=C:\MyFolder"
Vincent Therry
added a comment - Also I noticed I cannot set environment variables like that (I work on Windows) :
environment {
PATH_TO_MY_WINDOWS_FOLDER = "C:\\MyFolder"
}
I am getting the following error :
hudson.remoting.ProxyException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
http://jenkins.eureka.lan:8080/blue/organizations/jenkins/DispatchAdminApi%2FDispatchAdminApi/detail/master/149/pipeline#log-25 Script4.groovy: 1: unexpected char: '\' @ line 1, column 30.
http://jenkins.eureka.lan:8080/blue/organizations/jenkins/DispatchAdminApi%2FDispatchAdminApi/detail/master/149/pipeline#log-26 "PATH_TO_MY_WINDOWS_FOLDER=C:\MyFolder" Yes, known bug - JENKINS-42748
Ok, Thank you, my JiraFu seems broken 
I'll open an issue for my previous case when I will have the time.
Vincent Therry
added a comment - Ok, Thank you, my JiraFu seems broken
I'll open an issue for my previous case when I will have the time.
Bulk closing resolved issues.
One risk of a fix I've got almost done is that it could turn
environment { FOO = "foo" BAR = "${env.FOO} and env.Should not change" }into BAR == "foo and Should not change" - so I'm poking around to make sure I can do that replacement solely in the curlies.