On Wed, May 27, 2015 at 1:39 PM, Boris Chavez-Bravo
wrote:
> I think I have been able to get around this issue by wrapping the call to
> the script through a batch call:
>
> withEnv(["PATH=C:\\cygwin\\bin;%PATH%"]) {
> bat "C:\\cygwin\\bin\\bash ./my_script.sh ${arg1} ${arg2}"
> }
>
I don't mean
I think I have been able to get around this issue by wrapping the call to
the script through a batch call:
withEnv(["PATH=C:\\cygwin\\bin;%PATH%"]) {
bat "C:\\cygwin\\bin\\bash ./my_script.sh ${arg1} ${arg2}"
}
On Wednesday, May 27, 2015 at 1:07:41 PM UTC-4, LesMikesell wrote:
>
> On Thu, Jan 8
On Thu, Jan 8, 2015 at 12:35 PM, Jesse Glick wrote:
> On Friday, December 5, 2014 6:35:33 AM UTC-5, Rupali wrote:
>>
>> So I am concluding that Shell script in in workflow step is not working on
>> Windows slave.
>
>
> Or more precisely, that shell scripts run via durable-task-plugin (this also
>
Hi,
On 27.05.2015 17:03, Boris Chavez-Bravo wrote:
> I am facing the exact same issue. Has anyone come across a solution for
> this problem?
This smells like one of those cases where you should have been calling
"./script.sh", as the current directory is not on the search path for
very good re
I am facing the exact same issue. Has anyone come across a solution for
this problem?
On Thursday, January 8, 2015 at 1:35:42 PM UTC-5, Jesse Glick wrote:
>
> On Friday, December 5, 2014 6:35:33 AM UTC-5, Rupali wrote:
>>
>> So I am concluding that Shell script in in *workflow step* is not
>> w
On Friday, December 5, 2014 6:35:33 AM UTC-5, Rupali wrote:
>
> So I am concluding that Shell script in in *workflow step* is not working
> on Windows slave.
>
Or more precisely, that shell scripts run via durable-task-plugin (this
also includes the CloudBees Long-Running Build plugin) do not wo
I added a Linux slave today and ran the step to execute shell script on
Linux slave.
That worked well.
So I am concluding that Shell script in in *workflow step* is not working
on Windows slave.
Let me know if anyone thinks / knows otherwise.
Regards,
Rupali
On Thursday, December 4, 2014 11:41:
On Thu, Dec 4, 2014 at 10:47 AM, niraj nandane wrote:
> See to work all you need to provide bash path in global settings of jenkins
> as /bin/bash ..try out this...
>
If a jenkins windows slave is started by cygwin sshd, it doesn't seem
to propagate the jenkins variable settings. Is there a way
See to work all you need to provide bash path in global settings of jenkins
as /bin/bash ..try out this...
On Dec 2, 2014 9:20 PM, "Rupali" wrote:
> To debug further, I modified BourneShellScript.java file in DurableTask
> plugin to print the environment variables with which it is calling the
> s
To debug further, I modified BourneShellScript.java file in DurableTask
plugin to print the environment variables with which it is calling the
script.
I found that environment variables do not contain path to Cygwin as
observed in the output.
Can this be reason for the error I am seeing?
If ye
Hi,
I tried number of options but this is not working.
Does Shell script in workflow steps works only on Linux/Unix slaves?
Regards,
Rupali
On Monday, December 1, 2014 5:38:50 PM UTC+5:30, Rupali wrote:
>
> HI Ninad,
>
> Thank for the reply. But it doesn't work.
> Thing is, shell execution works
HI Ninad,
Thank for the reply. But it doesn't work.
Thing is, shell execution works well as part of normal Jenkins job, as a
build step.
But it fails to work when I add it as workflow step.
Not sure if workflow plugin has a different way to invoke shell scripts
than traditional Jenkins shell scr
Hi,
Install cygpath plugin and write
#/bin/bash before echo Hello statement
On Friday, November 28, 2014 3:09:05 PM UTC+5:30, Rupali wrote:
>
> Hi,
>
> I tried a simple command in shell script as below:
> sh 'echo Hello'
>
> It gives below error:
>
> [D:\Jenkins-Slave\workspace\Setup-WF] Running
Hi,
I tried a simple command in shell script as below:
sh 'echo Hello'
It gives below error:
[D:\Jenkins-Slave\workspace\Setup-WF] Running shell script
cygwin warning:
MS-DOS style path detected:
D:\Jenkins-Slave\workspace\Setup-WF\.fb8e6a28\pid
Preferred POSIX equivalent is:
/cygdrive/d/J
s.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:100)
>
>
> at
> com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:76)
>
>
> at sun.reflect.NativeMethodA
/jenkinsci/workflow-plugin-pipeline-demo/blob/master/flow.groovy
Thanks for your help in advance!
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/workflow-plugin-error-tp4726187.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
You received this mess
16 matches
Mail list logo
