[JIRA] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows

[londi...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Londino edited a comment on  JENKINS-16176  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ShiningPanda PATH update uses wrong separator on Windows   
 

  
 
 
 
 

 
 I have encountered this bug as well. It's not trivial to troubleshoot unless you stumble upon this issue, and it's not an uncommon problem to want to test Python code across Windows and Linux , which necessitates a mismatch in the OS between the master and the slave .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows

[londi...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Londino commented on  JENKINS-16176  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ShiningPanda PATH update uses wrong separator on Windows   
 

  
 
 
 
 

 
 I have encountered this bug as well. It's not trivial to troubleshoot unless you stumble upon this issue, and it's not an uncommon problem to want to test Python code across Windows and Linux.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows

[dbac...@dustnetworks.com (JIRA)]

Dave Bacher
 created  JENKINS-16176


ShiningPanda PATH update uses wrong separator on Windows















Issue Type:


Bug



Assignee:


Unassigned


Components:


shiningpanda



Created:


19/Dec/12 10:37 PM



Description:


When running ShiningPanda on a Windows slave, the plugin (or virtualenv?) updates the PATH to include the virtualenv directory. 

0. Install ShiningPanda plugin (this result is for v1.15)
1. Create a build with a Virtualenv build step
2. Use the Shell or XShell command with a minimal script:


set 
pip.exe install -r pkg_requirements.txt


The build fails because the pip command can not be found. The output shows the Path environment variable uses the : (colon) separator for the virtualenv Scripts directory. On Windows, the PATH separator should be ; (semicolon). 


[1-SMSDK-apps-venv] $ cmd.exe /c call C:\DOCUME~1\builder\LOCALS~1\Temp\shiningpanda4030889806584404855.bat

c:\jenkins-dev\workspace\1-SMSDK-apps-venv>set
... [edited for relevance] ...
Path=c:\jenkins-dev\workspace\1-SMSDK-apps-venv:c:\jenkins-dev\shiningpanda\deb23754\virtualenvs\d41d8cd9\Scripts:C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\FLEXlm;C:\Program Files\CollabNet\Subversion Client;c:\cygwin\bin;c:\cygwin\usr\bin;C:\Program Files\Java\jre6\bin
PYTHON_EXE=c:\jenkins-dev\shiningpanda\deb23754\virtualenvs\d41d8cd9\Scripts\python.exe
VIRTUAL_ENV=c:\jenkins-dev\shiningpanda\deb23754\virtualenvs\d41d8cd9
WORKSPACE=c:\jenkins-dev\workspace\1-SMSDK-apps-venv

c:\jenkins-dev\workspace\1-SMSDK-apps-venv>pip.exe install -r pkg_requirements.pip 
'pip.exe' is not recognized as an internal or external command,
operable program or batch file.





Environment:


Linux master, Windows XP slave with Python 2.7




Project:


Jenkins



Priority:


Major



Reporter:


Dave Bacher

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira