-
Bug
-
Resolution: Unresolved
-
Critical
-
None
My jenkins version is ver. 1.493 .
the command can run in cmd model and can normally end. you can see the log1 below.
But I put the command into the execute windows batch command, and then I run the job,the job hold on and can't end wait for long times. You can see the log2 below. I manually execute the bat file "C:\Users\Admin\AppData\Local\Temp\hudson9214056810875413252.bat" in cmd model . it can end.
– log1
C:\Users\Admin>PSEXEC -accepteula -s
GPS68 SCHTASKS /QUERY /TN "\GOPP\SDT" |findstr "Disabled"
PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com
Starting SCHTASKS on GPS68 ...GPS68 ...
SCHTASKS exited on GPS68 with error code 0.
SDT Disabled
--log2
[workspace] $ cmd /c call C:\Users\Admin\AppData\Local\Temp\hudson9214056810875413252.bat
D:\Jenkins\jobs\tsd_test\workspace>PSEXEC -accepteula
GPS68 SCHTASKS /QUERY /TN "\GOPP\SDT" | findstr "Disabled"
PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com
Hi dzy dzy.
I do not think there is any bug in this, but either PSEXEC or SCHTASK is waiting for some input
Is the jenkins job / service running with your credentials or does it run as LocalSystem ?
I am also wondering if your job is the actual job or are you testing PSEXEC ?
If it the real job, and you want you jenkins, to check - on a remote machine - if the remote machine's scheduled task named SDT is disabled, I would suggest 2 different approaches to you:
A) Install a jenkins slave on the remote machine, and create a job tied to that slave, the job shall then do what you wanted to do in the scheduled task
or
B) use schtasks with it's /S parameter:
Parameter List:
/S system Specifies the remote system to connect to.
/U username Specifies the user context under
which schtasks.exe should execute.
/P [password] Specifies the password for the given
user context. Prompts for input if omitted.