Short form: When running a tool on a remote machine via psexec, the output of the tool is generated when run from a command prompt, but is missing when invoked from Bamboo.
<strong>psexec.exe -accepteula (remote) (tool.exe)</strong>
Starting PSEXESVC service on (remote)...
Connecting with PsExec service on (remote)...
Starting (tool.exe) on (remote)...
(tool output shows here in command prompt, is missing in bamboo log...)
(tool.exe) exited on (remote) with error code 0.
Long form: I have a tool I'm wanting to execute on a remote machine during an automated build. It works, but every once in a while, it locks up, and in turn would lock up the build, since it never exits. I've added logging to the console in the tool, in hopes of tracking down what's happening. If I start up a command prompt using the same identity as the bamboo service, and call psexec (as above), the tool output to the console displays just fine.
Unfortunately, when the same command is called during a bamboo build (via the Bamboo SCRIPT task), the psexec runs the tool, and the tool executes, but none of the console logging is being recorded in the bamboo logs.
I'm using the latest psexec (2.11).
Anybody have any luck seeing the remotely executed tools output within Bamboo's logs?
Can someone explain to me the apparent idiosyncratic differences between calling psexec via a command prompt versus how Bamboo invokes it within its SCRIPT task?
