Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Run a build via the Windows Subsystem for Linux on Windows 10

I'm trying to test running jobs in bamboo which invoke a script using the bash.exe from the WSL on Windows 10 (without much luck). In my test bamboo is running on a local account as a service which also happens to be my account (for testing). I have ubuntu bash shells open so-as to keep the WSL alive. I created a simple .sh script which does :

echo "hello world"

Then in my task I setup the WSL bash as an executable ("c:\Windows\System32\bash.exe") and create a command task using that executable with arguments:

`-c "/mnt/c/path/to/my/"`

When I run it.. it just hangs. Does anyone have experience getting this to work? Thoughts?


1 answer

0 votes
Jeyanthan I Atlassian Team Sep 15, 2017


Did you get any clue from the Build logs? Maybe it gives you a clue on why it hangs.

I suggest you to use script task in your plan and invoke your script like below by choosing powershell as the interpreter.

bash ./

I actually didn't find anything helpful in the build logs. I also tried using a script task. In each case it hangs as soon as wsl bash.exe is called. It actually hung all night when I left it to run.

At this point I would like to recreate the mechanism for how the call to bash or the script is made in a small test which mimics the way bamboo does it. My guess is that there is something about the calling context/environment which doesn't work with WSL.

I guess it is because powershell doesn't close it's output stream properly and thus Bamboo wouldn't get exit 0 or 1 to decide if the task is a pass or fail. Check if this KB helps -  Powershell script hangs.

You should basically add a '-inputformat none' to the command argument.

-inputformat none -command


Filed a feature request to track this (although this is not officially supported) - BAM-18870

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

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 ...

223 views 4 6
Read article

Community Events

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

Events near you