I have a task in a a build plan that is failing because the return code is not zero.
The task itself is psexec command that kicks off batch file on a remote server.
```C:\Tools\PSTools\psexec -accepteula \\x.x.x.x -u LOADUI\jmeter -p xxxxxxx -s -d c:\jmeter.bat```
It looks like it is returning the PID of the psexec command into Bamboo and failing the task since it is expecting 0 as the result.
The error message is:
Failing task since return code of [C:\Users\Bamboo\bamboo-agent-home\temp\RXS-RXWAPI6-JOB1-457-ScriptBuildTask-330809019821038145.bat] was 13572 while expected 0
How can I fix this?
Hi @Aron Hansson,
Looking at the command you are running I'm going to assume that you are running this on Windows. Are you using the cmd or Powershell interpreter? What you can do either way is wrap the psexec command in a script (that you either check into the repo or reference externally, and modify the script task to call that script. that way you have a bit more control over how the execution of the script exits.
I hope that helps!
Thanks for the help. That's right, it's running on a Windows agent that connects to a remote Windows server with psexec to kick off a load test.
I was using the cmd interpreter in the task. If I wrap the command, how can I then manipulate the return code to have it pass the task?
G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events