git is not set to %path% on Win7x32bit slave machine

16 views
Skip to first unread message

Beilin Zhong

unread,
Jun 7, 2016, 4:46:12 AM6/7/16
to Jenkins Users

Hi           

I encounter a Jenkins problem as below, anyone has idea about this?

 

The Jenkins master is a Windows Server 2012 64bit machine, with git 1.8.3-preview20130601  installed in C:\Program Files (x86)\Git                                                                                                                                                                                                                                      

The Jenkins git global setting as below:


 

The slave is a Window7 32bit machine, with git version 2.8.3 installed in C:\Program Files\Git      

When I run set in the slave machine, I can see the git is set to %path%

                                                                                                                                                                                                                                      

But when I run set in Execute Windows batch command from Jenkins job, there is not git in %path%

09:06:20 Building remotely on EmbeddedHubWin7x32-9d2b402e-226a-4a78-9744-f85fd7edb0ed (EmbeddedHubWin7x32 swarm) in workspace C:\Jenkins\workspace\linda_datahub.embeddedHub.test\bits\x86\label\EmbeddedHubWin7x32
09:06:28 Copied 1 artifact from "linda_datahub.embeddedHub.manual.trigger" build number 39
09:06:28 [EmbeddedHubWin7x32] $ cmd /c call C:\Users\ADMINI~1\AppData\Local\Temp\hudson4954546427824731044.bat
09:06:29 ALLUSERSPROFILE=C:\ProgramData
09:06:29 APIType=HubAPI
09:06:29 APPDATA=C:\Users\Administrator\AppData\Roaming
09:06:29 bits=x86
09:06:29 BUILD_DISPLAY_NAME=topic-run-api-on-embeddedhub-TIC-5741.build.1 #38
09:06:29 BUILD_ID=38
09:06:29 BUILD_NUMBER=38
09:06:29 BUILD_TAG=jenkins-linda_datahub.embeddedHub.test-bits=x86,label=EmbeddedHubWin7x32-38
09:06:29 BUILD_URL=http://ticjenkins.skytapbuilddb.local:8080/tic/job/linda_datahub.embeddedHub.test/bits=x86,label=EmbeddedHubWin7x32/38/
09:06:29 CLEANUP_WORKSPACE=true
09:06:29 CommonProgramFiles=C:\Program Files\Common Files
09:06:29 COMPUTERNAME=EMBEDDED-HUB-X3
09:06:29 ComSpec=C:\Windows\system32\cmd.exe
09:06:29 COPYARTIFACT_BUILD_NUMBER_LINDA_DATAHUB_EMBEDDEDHUB_MANUAL_TRIGGER=39
09:06:29 DEBUG=true
09:06:29 EMBEDDED_HUB_PATH=3.0.0.100
09:06:29 EXECUTOR_NUMBER=0
09:06:29 FileServer=\\10.6.208.3\Share
09:06:29 FP_NO_HOST_CHECK=NO
09:06:29 GIT_BUILD_TAG=topic-run-api-on-embeddedhub-TIC-5741.build.1
09:06:29 HOMEDRIVE=C:
09:06:29 HOMEPATH=\Users\Administrator
09:06:29 HubAPI_TEST_PLAN=All
09:06:29 HUDSON_COOKIE=8ce81744-a836-499b-8772-744bb2b1a4c2
09:06:29 HUDSON_HOME=C:\Jenkins
09:06:29 HUDSON_SERVER_COOKIE=4be602ca8a2af4b7
09:06:29 HUDSON_URL=http://ticjenkins.skytapbuilddb.local:8080/tic/
09:06:29 JAVA=c:\Program Files\Java\jre7\bin\java.exe
09:06:29 JenkinsAccount=admin
09:06:29 JenkinsPassword=Quest123
09:06:29 JENKINS_HOME=C:\Jenkins
09:06:29 JENKINS_SERVER_COOKIE=4be602ca8a2af4b7
09:06:29 JENKINS_URL=http://ticjenkins.skytapbuilddb.local:8080/tic/
09:06:29 JOB_NAME=linda_datahub.embeddedHub.test/bits=x86,label=EmbeddedHubWin7x32
09:06:29 JOB_URL=http://ticjenkins.skytapbuilddb.local:8080/tic/job/linda_datahub.embeddedHub.test/bits=x86,label=EmbeddedHubWin7x32/
09:06:29 label=EmbeddedHubWin7x32
09:06:29 LOCALAPPDATA=C:\Users\Administrator\AppData\Local
09:06:29 LOGONSERVER=\\EMBEDDED-HUB-X3
09:06:29 MASTER=jenkins.skytap.quest.corp
09:06:29 MSI_JOB_NAME=linda_datahub.embeddedHub.manual.trigger
09:06:29 NODE_LABELS=EmbeddedHubWin7x32 EmbeddedHubWin7x32-9d2b402e-226a-4a78-9744-f85fd7edb0ed swarm
09:06:29 NODE_NAME=EmbeddedHubWin7x32-9d2b402e-226a-4a78-9744-f85fd7edb0ed
09:06:29 NUMBER_OF_PROCESSORS=2
09:06:29 OS=Windows_NT
09:06:29 Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
09:06:29 PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
09:06:29 PROCESSOR_ARCHITECTURE=x86
09:06:29 PROCESSOR_IDENTIFIER=x86 Family 6 Model 37 Stepping 1, GenuineIntel
09:06:29 PROCESSOR_LEVEL=6
09:06:29 PROCESSOR_REVISION=2501
09:06:29 ProgramData=C:\ProgramData
09:06:29 ProgramFiles=C:\Program Files
09:06:29 PROMPT=$P$G
09:06:29 PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
09:06:29 PUBLIC=C:\Users\Public
09:06:29 SESSIONNAME=Console
09:06:29 SKYTAPCONFIG=8569048
09:06:29 SWARMJAR=c:\Jenkins\swarm-client-1.15-jar-with-dependencies.jar
09:06:29 SystemDrive=C:
09:06:29 SystemRoot=C:\Windows
09:06:29 TEMP=C:\Users\ADMINI~1\AppData\Local\Temp
09:06:29 TestAccount=FILESERVER\BuildAccess
09:06:29 TestPassword=FixBoardName!
09:06:29 TestVMLoginAccount=administrator
09:06:29 TestVMLoginPassword=FixBoardName!
09:06:29 TMP=C:\Users\ADMINI~1\AppData\Local\Temp
09:06:29 USERDOMAIN=EMBEDDED-HUB-X3
09:06:29 USERNAME=Administrator
09:06:29 USERPROFILE=C:\Users\Administrator
09:06:29 windir=C:\Windows
09:06:29 windows_tracing_flags=3
09:06:29 windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log
09:06:29 WORKSPACE=C:\Jenkins\workspace\linda_datahub.embeddedHub.test\bits\x86\label\EmbeddedHubWin7x32

 

 

Mark Waite

unread,
Jun 7, 2016, 10:19:05 AM6/7/16
to Jenkins Users
I believe the Windows PATH settings depend on the technique used to launch the slave.  If the slave is launched as a service, then it will have the system PATH settings but not the PATH settings from your user account.  If the slave is launched as a JNLP slave (from the Jenkins web page for that node), then it will have the user account PATH settings that were effective at the time the slave was started.

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/83b4cbb1-d198-404f-a196-bdde32bac393%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages