[JIRA] (JENKINS-41890) Declarative syntax: ${env.WORKSPACE} not set in environment block

p.garstenauer@sanitas.at (JIRA)

unread,

Feb 9, 2017, 7:45:01 AM2/9/17

to jenkinsc...@googlegroups.com

Paul Garstenauer created an issue

Jenkins /

JENKINS-41890

Declarative syntax: ${env.WORKSPACE} not set in environment block

Issue Type:	Bug
Assignee:	Unassigned
Components:	pipeline
Created:	2017/Feb/09 12:44 PM
Environment:	Windows
Labels:	declarative pipeline
Priority:	Minor
Reporter:	Paul Garstenauer

I got the following in my jenkins file:

pipeline {
agent any

environment {
SOURCE = "$

{env.WORKSPACE}
mydirectory"
// The above is not working? WORKSPACE is null as you can see later.
HTDOCS = "C:\\Apache24\\htdocs
"
}

stages {
stage('Prepare') {
steps {
echo "WORKSPACE ${env.WORKSPACE}

" // correct
echo "SOURCE $

{env.SOURCE}

" // wrong, is set to null\myDirectoy
echo "INEW_HTDOCS $

{env.INEW_HTDOCS}

" // correct
}
}

....

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

andrew.bayer@gmail.com (JIRA)

unread,

Feb 9, 2017, 12:08:03 PM2/9/17

to jenkinsc...@googlegroups.com

Andrew Bayer resolved as Duplicate

Jenkins /

JENKINS-41890

Declarative syntax: ${env.WORKSPACE} not set in environment block

Change By:	Andrew Bayer
Status:	Open Resolved
Resolution:	Duplicate

Add Comment

andrew.bayer@gmail.com (JIRA)

unread,

Feb 9, 2017, 12:08:03 PM2/9/17

to jenkinsc...@googlegroups.com

Andrew Bayer updated an issue

Jenkins /

JENKINS-41890

Declarative syntax: ${env.WORKSPACE} not set in environment block

Change By:	Andrew Bayer
Component/s:	pipeline-model-definition-plugin
Component/s:	pipeline

Add Comment

andrew.bayer@gmail.com (JIRA)

unread,

Feb 9, 2017, 2:21:02 PM2/9/17

to jenkinsc...@googlegroups.com

Andrew Bayer reopened an issue

Reopening - while working on JENKINS-41748, I realized that this will still be a problem there, since we don't actually have a WORKSPACE yet at the time we do environment variable resolution.