[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title John Forrest commented on JENKINS-52847 Re: durable-task plugin v1.23 misbehaves on BusyBox agents Note JENKINS-52887 where use of bash shell on windows-based machines no longer works. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52881) durable-task plugin v1.23 kills jobs on Cygwin/MSys agents
Title: Message Title John Forrest commented on JENKINS-52881 Re: durable-task plugin v1.23 kills jobs on Cygwin/MSys agents I'm seeing this too. Jenkins master is on centos7. Slave is running on a Windows Server 2016 but (among other things) I'm using the docker plugin which in turn using git shell. I do have downgraded the durable task plugin - I tried the suggestion of setting: -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=600 in /etc/sysconfig/jenkins, and it made no difference. My guess is that despite the message it is the error on the ps that is being reacted to. The alternative workaround for me would be to stop using the docker plugin. Originally, before I worked out how to use "sh" from Jenkins on a PC (ensure git is installed to C:\git and add C:\git\usr\bin to the windows path), I did have some code that tried to build on windows via bat - basically doing it all myself. I'd prefer not to have to - problem cases to handle etc etc. If this does not get fixed I probably will. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49655) Limit to number of steps shown per parallel section
Title: Message Title John Forrest updated an issue Jenkins / JENKINS-49655 Limit to number of steps shown per parallel section Change By: John Forrest I've a scripted pipeline structure that forks and builds multiple modules, depending on how it is started. The main build is via cmake, but there are often several steps first - e.g. fixing git repos, pulling down binary dependencies etc. We've noticed that the cmake steps often now don't appear in the blue ocean view - although it you look at the overall log for the parallel step itself then it will be working, just not showing in the step view. It took a while to realise what is happening, but it seems that when the cmake steps don't show there are I recently changed the scripts so that there are more binaries that are pulled down and unpacked before the build proper. Seems that was the trigger for the cmake stuff not showing - the number depends on the module being built. Took a while to realise this.IT seems there is a maximum number of steps shown per parallel step and it is in the range 100-120 - I've not counted too closely. I am assuming this is a literal Could this be raised? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49655) Limit to number of steps shown per parallel section
Title: Message Title John Forrest created an issue Jenkins / JENKINS-49655 Limit to number of steps shown per parallel section Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-02-20 15:33 Environment: Jenkins ver. 2.89.4, BlueOcean 1.4.2 Priority: Major Reporter: John Forrest I've a scripted pipeline structure that forks and builds multiple modules, depending on how it is started. The main build is via cmake, but there are often several steps first - e.g. fixing git repos, pulling down binary dependencies etc. We've noticed that the cmake steps often now don't appear in the blue ocean view - although it you look at the overall log for the parallel step itself then it will be working, just not showing in the step view. It took a while to realise what is happening, but it seems that when the cmake steps don't show there are I recently changed the scripts so that there are more binaries that are pulled down and unpacked before the build proper. Seems that was the trigger for the cmake stuff not showing - the number depends on the module being built. Took a while to realise this. IT seems there is a maximum number of steps shown per parallel step and it is in the range 100-120 - I've not counted too closely. I am assuming this is a literal Could this be raised?
