Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo Inline psexec Script Task Fails b/c Return Code

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?

1 answer

0 votes
Jimmy Seddon Community Leader Dec 11, 2019

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!


Hi Jimmy, 

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? 

Jimmy Seddon Community Leader Dec 12, 2019

Hi @Aron Hansson,

What we normally do is put the command we want to execute into at try/catch

and then if we hit an exception while running the command.  We throw an error that will exit the script with an non-zero status.


Like William likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events