Hi Guys!
Thanks for shared the solutions! I was in the same.
Do you know why JENKINS-41339 is close as resolved if the problem is there?
Thanks again,
Nico.
El sábado, 11 de febrero de 2017, 13:22:35 (UTC-3), John Mellor escribió:
>
> After downgrading the durable tasks pluginto fix this
After downgrading the durable tasks pluginto fix this problem, a manual
reboot is required to actually get pipelines functional again. Thanks,
Daniel !
On Friday, 10 February 2017 17:08:25 UTC-5, Daniel Beck wrote:
>
>
> > On 10.02.2017, at 21:40, John Mellor
> wrote:
>
> On 10.02.2017, at 21:40, John Mellor wrote:
>
> Now what? All pipelines a inoperable at this point.
I linked to JENKINS-41339 earlier, which mentions solutions in the comments.
--
You received this message because you are subscribed to the Google Groups
"Jenkins
Looking at your pipeline plugin version numbers, I assume that you are on
Jenkins2.
I'm on Jenkins 1.656 and have been unable to move up to the exact pipeline
plugin version numbers that you used.
However, I have the same problem, and unfortunately reverting to the
previous version has not
Yes that is what the issue is -- thank you.
I have provided some information about downgrading -- however I have not
run a full system test that will prove that it works on OSX, Linux, Sparc
and windows -- If It does I will reply back.
On Thursday, January 26, 2017 at 8:57:25 AM UTC-5, Daniel
I downgraded the following plugins, jenkins claimed that i did not need to
restart so I didn't and tested each individually, the code below still
failed. So I rebooted at the end and it worked so another bug. I am not
sure if one or more than one need to be downgraded. Some of the downgrades
> On 25.01.2017, at 23:30, Rinaldo DiGiorgio wrote:
>
> nohup: failed to run command ‘sh’: No such file or directory
Could this be https://issues.jenkins-ci.org/browse/JENKINS-41339 ?
--
You received this message because you are subscribed to the Google Groups
The lack of exception information or any textual indication as to the component
that failed is another issue. How is one supposed to figure out what to
downgrade. Here we are two days into it and we still can’t fix it without
extensive trial and error. Where is the sh step defined. Having an
Am Mittwoch, 25. Januar 2017 23:30:07 UTC+1 schrieb Rinaldo DiGiorgio:
>
> The following code was working with 2.41 ( maybe it was 2.40 )
>
> node("master") {
>sh 'ls'
> }
>
>
> I get the following error
>
> Running on master in /scratch/mach5-j/jenkins/jobs/sh
> issue/workspace[Pipeline]
The following code was working with 2.41 ( maybe it was 2.40 )
node("master") {
sh 'ls'
}
I get the following error
Running on master in /scratch/mach5-j/jenkins/jobs/sh issue/workspace[Pipeline]
{[Pipeline] sh[workspace] Running shell script
nohup: failed to run command ‘sh’: No such file
10 matches
Mail list logo