[JIRA] (JENKINS-37508) Can't see where "Exported variables" get defined

Issue Type:	Bug
Assignee:	Oleg Nenashev
Components:	customtools-plugin
Created:	2016/Aug/18 9:51 AM
Environment:	Jenkins 2.18, Windows 7 x64
Labels:	environment-variables
Priority:	Minor
Reporter:	David Bilsby

I have defined a couple of custom tools for various jobs so I can use defined environment variables in various job scripts. The tools are all pre-installed on the build machine so I'm not using the "Install automatically" feature. I have named the tools, added the "Exported paths", "Installation directory" and also added various "Exported variables" of the format:

TOOL_VAR_NAME=fred
TOOL_VAR_VERSION=bob

When I run the job which enables the named tool I do not see any of the variables in the build environment, displayed via a Windows DOS "SET" command, for any of the "Exported variables" I have defined. I also don't see the "Exported paths" being added to the system PATH which I thought it was supposed to be. I do the "Setting <TOOLNAME>_HOME=<blarh>" in the job log and the <TOOLNAME>_HOME variable in the environment however.

Am I missing something here?

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

dcbilsby1@qinetiq.com (JIRA)

unread,

Aug 18, 2016, 6:20:01 AM8/18/16

to jenkinsc...@googlegroups.com

David Bilsby resolved as Not A Defect

Apologies, mix up between Custom Tools and Tool Environment plugins. Sorted issue, my mistake.

Jenkins /

Change By:	David Bilsby
Status:	Open Resolved
Resolution:	Not A Defect

bruder@bruder.dk (JIRA)

unread,

Mar 20, 2019, 2:00:02 PM3/20/19

to jenkinsc...@googlegroups.com

Jesper Matthiesen commented on

Re: Can't see where "Exported variables" get defined

I don't understand what the mentioned mixup is about, but I have the exact same issue with the custom tools plugin. Nothing I set is visible during the build when viewed through bat "set".

Shouldn't at least stuff in Exported Paths be visible in the PATH env variable?

If I e.g. create a custom tool named 'VSTest' and set the following:

Installation directory 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools'

Exported paths 'Common7\IDE\Extensions\TestPlatform'

I would expect the PATH to contain 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\Extensions\TestPlatform'

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

daniel.hoerner@vyaire.com (JIRA)

unread,

May 7, 2019, 9:36:02 AM5/7/19

to jenkinsc...@googlegroups.com

Daniel Hoerner reopened an issue

Same problem here.

I have NOT installed the Tool Envoronment plugin.

Added following to the Custom Tool Definition:

Exported Paths: "C:\Program Files\nodejs"

But I can not see this path when running the "set" command of Windows durring build:

 
                                                                // node('VS2017') {
stage('Preparing Build machine...')
    {  
        tool name: 'npm 6.4.1', type: 'com.cloudbees.jenkins.plugins.customtools.CustomTool' 
    }
echo "Current Environment:"
bat 'set'
}
 
                                                            

Jenkins /

Change By:	Daniel Hoerner
Resolution:	Not A Defect
Status:	Resolved Reopened

daniel.hoerner@vyaire.com (JIRA)

unread,

May 7, 2019, 9:37:04 AM5/7/19

to jenkinsc...@googlegroups.com

Daniel Hoerner updated an issue

Jenkins /

Change By:	Daniel Hoerner
Priority:	Minor Major

daniel.hoerner@vyaire.com (JIRA)

unread,

May 7, 2019, 9:39:01 AM5/7/19

to jenkinsc...@googlegroups.com

Daniel Hoerner edited a comment on

Re: Can't see where "Exported variables" get defined

Same problem here.

I have NOT installed the Tool Envoronment plugin.

Added following to the Custom Tool Definition:

Exported Paths: "C:\Program Files\nodejs"

I using the custom tool installer durring the runtime at the Build VM (See Preparing Build machine stage)

But I can not see this path when running the "set" command of Windows durring build:

{code:java}

// node('VS2017') {
stage('Preparing Build machine...')
    {
        tool name: 'npm 6.4.1', type: 'com.cloudbees.jenkins.plugins.customtools.CustomTool'
    }
echo "Current Environment:"
bat 'set'
}

{code}