Re: Command not found error on bash build script

2015-12-02 Thread Gouri Nair
Thank you. I will get rid of the spaces. I am new to bash scripting hence i made that mistake. On Wednesday, December 2, 2015 at 9:24:08 AM UTC-8, John Mellor wrote: > > Gouri quoted: > > . . . > > then > > partnerfolder = "update" > > . . . > > > > Why do you have spaces around the assignm

Re: Command not found error on bash build script

2015-12-02 Thread Gouri Nair
Thank you. I will keep that in mind. On Wednesday, December 2, 2015 at 9:01:02 AM UTC-8, Daniel Beck wrote: > > > On 02.12.2015, at 17:38, Gouri Nair > > wrote: > > > Can someone tell me what could be wrong? > > Has absolutely nothing to do with Jenkins. It's just invalid bash syntax. > Get ri

RE: Command not found error on bash build script

2015-12-02 Thread John Mellor
Gouri quoted: . . . then partnerfolder = "update" . . . Why do you have spaces around the assignment operator? That’s not legal in bash or any other normal shell language. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Gouri Nair Sent: Decemb

Re: Command not found error on bash build script

2015-12-02 Thread Daniel Beck
On 02.12.2015, at 17:38, Gouri Nair wrote: > Can someone tell me what could be wrong? Has absolutely nothing to do with Jenkins. It's just invalid bash syntax. Get rid of the space around the '=' char. In the future, try whether what you're doing works outside Jenkins before asking for help.