[ 
https://issues.jenkins-ci.org/browse/JENKINS-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162094#comment-162094
 ] 

gbois commented on JENKINS-13616:
---------------------------------

Do you have defined $ProgramFiles variable somewhere?
Could you attach your job configuration file (config.xml)?
                
> Environment variables not expanded in CMake build steps
> -------------------------------------------------------
>
>                 Key: JENKINS-13616
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13616
>             Project: Jenkins
>          Issue Type: Bug
>          Components: cmakebuilder, envinject
>    Affects Versions: current
>            Reporter: Anthony Berent
>            Assignee: gbois
>
> I have a number of projects that, on windows, use cmake build commands 
> including environment variables, such as:
>  
> "${ProgramFiles}\Microsoft Visual Studio 9.0\vc\vcpackages\vcbuild.exe" 
> TCtoolCMake.sln "Release|Win32" 
> This worked until I upgraded Jenkins quite recently to version 1.460 (and I 
> think upgraded the envinject plugin at the same time), but no longer works. I 
> am using cmakebuild 1.9 and envinject 1.46.
> I can work around this by changing the command to
> "c:\Program Files\Microsoft Visual Studio 9.0\vc\vcpackages\vcbuild.exe" 
> TCtoolCMake.sln "Release|Win32" 
> but this is less portable between machines (e.g. I don't think it will work 
> on a Windows 7 machine). 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to