The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

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

Calvin Ngu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 7, 2019

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Jimmy Seddon
Community Champion
May 8, 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

Calvin Ngu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 9, 2019

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 Champion
May 9, 2019

Hey Calvin,

I'm glad that fixed things for you!

-James

TAGS
AUG Leaders

Atlassian Community Events