> On 25.02.2017, at 04:21, Sharan Basappa wrote:
>
> Maybe it is not related but one thing I changed recently was the native
> shell. I changed from sh to csh
Should be easy enough to test with a shebang line at the beginning of the `sh`
argument.
--
You received this message because you ar
> On 25.02.2017, at 06:59, David Karr wrote:
>
> Stage takes a closure.
Originally they weren't. This was added recently (JENKINS-26107) and while
AFAIK deprecated, the old syntax should still work.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users"
I'll say again, add braces around the body of the entire stage. Stage takes
a closure.
On Fri, Feb 24, 2017, 19:21 Sharan Basappa wrote:
> David,
>
> I will remove everything and start with just pwd. I will update how it
> goes.
> Maybe it is not related but one thing I changed recently was the
David,
I will remove everything and start with just pwd. I will update how it goes.
Maybe it is not related but one thing I changed recently was the native
shell. I changed from sh to csh
On Friday, 24 February 2017 17:39:07 UTC+5:30, Daniel Beck wrote:
>
> > On 21.02.2017, at 19:09, Sharan Bas
> On 21.02.2017, at 19:09, Sharan Basappa wrote:
>
> Snippet of Jenkins log:
>
Is that the minimal Pipeline script exhibiting the problem, i.e. is the git
checkout necessary? What happens when you remove everything but the 'sh "pwd"'
that doesn't work, does it work then?
--
You received th
Hi David,
Is there any other forum where I can get help? I haven't got much inputs on
this forum
On Fri, Feb 24, 2017 at 12:08 AM, David Karr
wrote:
> On Wed, Feb 22, 2017 at 9:36 AM, Sharan Basappa
> wrote:
> > folks, need some guidance here ... thanks
> >
> > On Tuesday, 21 February 2017 23:
On Wed, Feb 22, 2017 at 9:36 AM, Sharan Basappa
wrote:
> folks, need some guidance here ... thanks
>
> On Tuesday, 21 February 2017 23:39:43 UTC+5:30, Sharan Basappa wrote:
>>
>> My Jenkins build job indicates success but none of the scripts I am
>> executing seem to do anything. I put a simple "p
folks, need some guidance here ... thanks
On Tuesday, 21 February 2017 23:39:43 UTC+5:30, Sharan Basappa wrote:
>
> My Jenkins build job indicates success but none of the scripts I am
> executing seem to do anything. I put a simple "pwd" command to echo current
> working directory but nothing ha
My Jenkins build job indicates success but none of the scripts I am
executing seem to do anything. I put a simple "pwd" command to echo current
working directory but nothing happens. All Jenkins reports is "Running
shell script" and then nothing is seen.
Snippet of Jenkins log:
First time bu
