|
||||||||
|
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 |
||||||||
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
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.