-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins Master:
version 2.26
Linux
JDK 1.7 for the JVM
Swarm plugin 2.2
Slave:
Swarm jar 2.0
Windows 2008
I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine (presumably with previous versions of jenkins and plugins)
Today (haven't used these jobs in a while) I see this in the output (I run "echo Path is %PATH%" in a Windows batch step)
>echo "Path is e:\jenkins\jdk\JDK_1.7/bin;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319"
%PATH% is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see screenshot.
I don't know for certain whether it is the swarm plugin or jenkins tool provider core doing this.
[JENKINS-39359] Tool Locations published from swarm client on windows are appended with forward slash
Description |
Original:
I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine. Today (haven't used these jobs in a while) I see this in the output (I run "echo Path is %PATH%" in a Windows batch step) >echo "Path is *e:\jenkins\jdk\JDK_1.7/bin*;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319" The PATH is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see screenshot. I don't know for certain whether it is the swarm plugin or jenkins tool provider core doing this. |
New:
I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine. Today (haven't used these jobs in a while) I see this in the output (I run "echo Path is %PATH%" in a Windows batch step) {quote} >echo "Path is *e:\jenkins\jdk\JDK_1.7/bin*;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319" {quote} The PATH is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see screenshot. I don't know for certain whether it is the swarm plugin or jenkins tool provider core doing this. |
Description |
Original:
I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine. Today (haven't used these jobs in a while) I see this in the output (I run "echo Path is %PATH%" in a Windows batch step) {quote} >echo "Path is *e:\jenkins\jdk\JDK_1.7/bin*;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319" {quote} The PATH is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see screenshot. I don't know for certain whether it is the swarm plugin or jenkins tool provider core doing this. |
New:
I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine (presumably with previous versions of jenkins and plugins) Today (haven't used these jobs in a while) I see this in the output (I run "echo Path is %PATH%" in a Windows batch step) {quote} >echo "Path is *e:\jenkins\jdk\JDK_1.7/bin*;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319" {quote} The PATH is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see screenshot. I don't know for certain whether it is the swarm plugin or jenkins tool provider core doing this. |
Description |
Original:
I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine (presumably with previous versions of jenkins and plugins) Today (haven't used these jobs in a while) I see this in the output (I run "echo Path is %PATH%" in a Windows batch step) {quote} >echo "Path is *e:\jenkins\jdk\JDK_1.7/bin*;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319" {quote} The PATH is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see screenshot. I don't know for certain whether it is the swarm plugin or jenkins tool provider core doing this. |
New:
I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine (presumably with previous versions of jenkins and plugins) Today (haven't used these jobs in a while) I see this in the output (I run *"echo Path is %PATH%"* in a Windows batch step) {quote} >echo "Path is *e:\jenkins\jdk\JDK_1.7/bin*;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319" {quote} %PATH% is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see *screenshot*. I don't know for certain whether it is the swarm plugin or jenkins tool provider core doing this. |
Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] |
As a workaround I replace / with \ like this in the batch step:
PATH="%PATH:/=\%"
Obviously this only works for this batch step and thus does not help things like maven/gradle steps.