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

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

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

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

Or

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.

 

Thanks.

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.

-James

Hi James,

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

 

Thanks,

Calvin

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

Hey Calvin,

I'm glad that fixed things for you!

-James

Suggest an answer

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

Bamboo 7.1 is here and is packed with value!

I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...

696 views 1 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