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

'#' is not recognized as an internal or external command


I have multiple deployment processes that run a (Shell - inline) script that starts with:

# a comment
if [[ ${bamboo_countryFile} =~ ^test ]]; then
and does an rsync at the end...

Sometimes I get the errors:

'#' is not recognized as an internal or external command, operable program or batch file.
${bamboo_countryFile} was unexpected at this time.


Host key verification failed.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(605) [sender=3.0.9]

The script is set on multiple deployment environments and the errors occur randomly on most of the environments when run concurrently, such as being triggered from a successful build/deployment. However, they are usually ok with no errors when the environments are run manually individually.



1 answer

1 accepted

0 votes
Answer accepted
Jimmy Seddon Community Leader May 08, 2019

Hi Calvin,

Just as a thought do you have multiple agents that are running these deployments and have you looked to see which agent happens to be running the job when it passes vs fails.

I only ask because this is how I found an agent I had forgotten to update with the latest version of a tool we use when jobs were randomly failing and it just happen to be luck of the draw as to which job ran though that agent.

Just something to think about.  I hope that helps you.


Hi James,

  Yes, it was agent related.  So after I specified a linux agent, it worked.




Like Jimmy Seddon likes this
Jimmy Seddon Community Leader May 09, 2019

Hey Calvin,

I'm glad that fixed things for you!


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events