[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou commented on JENKINS-59907 Re: sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Don L can we move this over to JENKINS-59903? That would be the relevant ticket. Could you also confirm that you are running v1.33? and not v1.31-32 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.777.1583522280331%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou commented on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container Tim Black So the differences of 1.29 and 1.33 should be fairly negligible. What happened between all those release was the introduction of a binary wrapper (to replace the shell wrapper) for shell scripts to make them more "durable". However, there were varied compatibility issues (mostly with docker and non-x86 builds) that we made the original shell wrapper the default behavior again. Your logging shows that the original shell wrapper is indeed running. The biggest difference I can see between yours and the OP is that your script appears to be executing (writing output to the jenkins-log.txt) and terminating with 0 as opposed to failure. Like I mentioned with OP, if you can run with LAUNCH_DIAGNOSTICS, that might help us get a better idea of what is going on. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.8271.1583435760205%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou commented on JENKINS-59907 Re: sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Rahul Raj it appears you are using x86, and not an "uncommon architecture" like this ticket is describing. I would probably advise setting LAUNCH_DIAGNOSTICS=true as suggested in the output log and that can tell us better. The default behavior for this plugin should be using the original script wrappers. If you can't ascertain what is going there, I would probably post this to jenkinsci-users mailing list while we're still investigating. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.1498.1582927500326%40Atlassian.JIRA.
[JIRA] (JENKINS-60550) Determine if heavyweight or lightweight checkout was used for multibranch pipelines
Title: Message Title Carroll Chiou updated an issue Jenkins / JENKINS-60550 Determine if heavyweight or lightweight checkout was used for multibranch pipelines Change By: Carroll Chiou Currently, SCMBinder will attempt to perform a lightweight checkout, falling back to heavyweight when that fails. There However, there is no public way to tell which type of checkout was use. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203654.1576795671000.1895.1578000360066%40Atlassian.JIRA.
[JIRA] (JENKINS-60550) Determine if heavyweight or lightweight checkout was used for multibranch pipelines
Title: Message Title Carroll Chiou updated an issue Jenkins / JENKINS-60550 Determine if heavyweight or lightweight checkout was used for multibranch pipelines Change By: Carroll Chiou Currently, SCMBinder will attempt to perform a lightweight checkout, falling back to heavyweight when that fails. There is no public way to tell which type of checkout was use. Maybe we can add an isLightweight() method like in CpsScmFlowDefinition? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203654.1576795671000.1894.1578000300171%40Atlassian.JIRA.
[JIRA] (JENKINS-60550) Determine if heavyweight or lightweight checkout was used for multibranch pipelines
Title: Message Title Carroll Chiou edited a comment on JENKINS-60550 Re: Determine if heavyweight or lightweight checkout was used for multibranch pipelines Making SCMBinder public may not be ideal though : https://github.com/jenkinsci/workflow-multibranch-plugin/pull/78 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203654.1576795671000.1893.1578000300156%40Atlassian.JIRA.
[JIRA] (JENKINS-60550) Determine if heavyweight or lightweight checkout was used for multibranch pipelines
Title: Message Title Carroll Chiou commented on JENKINS-60550 Re: Determine if heavyweight or lightweight checkout was used for multibranch pipelines Making SCMBinder public may not be ideal though: https://github.com/jenkinsci/workflow-multibranch-plugin/pull/78 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203654.1576795671000.1892.1578000300121%40Atlassian.JIRA.
[JIRA] (JENKINS-60550) Determine if heavyweight or lightweight checkout was used for multibranch pipelines
Title: Message Title Carroll Chiou updated an issue Jenkins / JENKINS-60550 Determine if heavyweight or lightweight checkout was used for multibranch pipelines Change By: Carroll Chiou Currently, SCMBinder will attempt to perform a lightweight checkout, falling back to heavyweight when that fails. There is no public way to tell which type of checkout was use. Propose adding Maybe we can add an isLightweight() method like in CpsScmFlowDefinition . ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203654.1576795671000.1891.1578000240056%40Atlassian.JIRA.
[JIRA] (JENKINS-60550) Determine if heavyweight or lightweight checkout was used for multibranch pipelines
Title: Message Title Carroll Chiou updated an issue Jenkins / JENKINS-60550 Determine if heavyweight or lightweight checkout was used for multibranch pipelines Change By: Carroll Chiou Summary: Let SCMBinder indicate Determine if heavyweight or lightweight checkout was used for multibranch pipelines Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203654.1576795671000.1890.1578000180071%40Atlassian.JIRA.
[JIRA] (JENKINS-60550) Let SCMBinder indicate if heavyweight or lightweight checkout was used
Title: Message Title Carroll Chiou updated an issue Jenkins / JENKINS-60550 Let SCMBinder indicate if heavyweight or lightweight checkout was used Change By: Carroll Chiou Currently, SCMBinder will attempt to perform a lightweight checkout, falling back to heavyweight when that fails. There is no public way to tell which type of checkout was use. Adding a basic Propose adding an isLightweight() method like in CpsScmFlowDefinition would be useful . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203654.1576795671000.1740.1577982480072%40Atlassian.JIRA.
[JIRA] (JENKINS-60550) Let SCMBinder indicate if heavyweight or lightweight checkout was used
Title: Message Title Carroll Chiou created an issue Jenkins / JENKINS-60550 Let SCMBinder indicate if heavyweight or lightweight checkout was used Issue Type: Improvement Assignee: Unassigned Components: workflow-multibranch-plugin Created: 2019-12-19 22:47 Priority: Minor Reporter: Carroll Chiou Currently, SCMBinder will attempt to perform a lightweight checkout, falling back to heavyweight when that fails. There is no public way to tell which type of checkout was use. Adding a basic isLightweight() method like in CpsScmFlowDefinition would be useful. Add Comment
[JIRA] (JENKINS-60140) Cannot run program "powershell" when powershell 6.0 core installed
Title: Message Title Carroll Chiou closed an issue as Not A Defect Closing as this issue was resolved in workflow-durable-task-step 2.35 Jenkins / JENKINS-60140 Cannot run program "powershell" when powershell 6.0 core installed Change By: Carroll Chiou Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.
[JIRA] (JENKINS-60107) durabletask v1.33 - process apparently never started in /var/lib/jenkins/workspace/local-cloud-regression-test@tmp/durable-fa896164
<<< text/html; charset="UTF-8": Unrecognized >>>
[JIRA] (JENKINS-60069) (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400)
Title: Message Title Carroll Chiou commented on JENKINS-60069 Re: (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400) Apologies, I also meant to ask if you could post of the error you are seeing when you run your pipeline. If you are on an x86 machine that is running *NIX, have you tried my earlier suggestion of passing in the property -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.FORCE_BINARY_WRAPPER=true? That might handle the laggy filesystem better because the binary does not poll the log file. I would also be curious to know if durable-task 1.30 exhibits the same problem for you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202903.1573010971000.10416.1573111440236%40Atlassian.JIRA.
[JIRA] (JENKINS-60069) (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400)
Title: Message Title Carroll Chiou commented on JENKINS-60069 Re: (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400) There's not much here in this ticket to go by. Can you post the Jenkinsfile? If you are on an x86 machine that is running *NIX, you can try passing in the property -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.FORCE_BINARY_WRAPPER=true Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202903.1573010971000.10336.1573081260255%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou commented on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container Just noting that the title is a bit misleading. If I read this right, it looks like you have a failed shell step and that it has not been working on 1.29, 1.30, and 1.33. It's not that the upgrade to 1.33 has broken your pipeline correct? Is there any way you can run your pipeline again with org.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true and posting the output here? That might give a better idea of what's going on. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.10328.1573080662937%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou updated JENKINS-60065
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Carroll Chiou
Status:
Open Fixed but Unreleased
Resolution:
Duplicate
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202898.1572987647000.10307.1573078620453%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou updated JENKINS-60065
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Carroll Chiou
Status:
Fixed but Unreleased Closed
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202898.1572987647000.10309.1573078620503%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou commented on JENKINS-60065
Re: durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
I believe this is related to https://issues.jenkins-ci.org/browse/JENKINS-59907 1.31 introduced an x86-based binary wrapper that would launch the shell scripts. Unfortunately, there was a bug that did not check whether the environment was indeed x86. Please upgrade the plugin to 1.33.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202898.1572987647000.10274.1573068660186%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou assigned an issue to Carroll Chiou
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Carroll Chiou
Assignee:
Carroll Chiou
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202898.1572987647000.10276.1573068660215%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou updated an issue
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Carroll Chiou
Environment:
Jenkins ver. 2.190.2master: Darwin xyz 17.6.0 Darwin Kernel Version 17.6.0: Tue May 8 15:22:16 PDT 2018; root:xnu-4570.61.1~1/RELEASE_X86_64 x86_64build slave info:Linux buildpi1 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linuxgetconf LONG_BIT -> 32OpenJDK Runtime Environment (build 1.8.0_212-8u212-b01-1+rpi1-b01) z
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202898.1572987647000.10270.1573068240258%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou resolved as Fixed Jenkins / JENKINS-59903 durable-task v1.31 breaks sh steps in pipeline when running in a Docker container Change By: Carroll Chiou Status: In Progress Resolved Resolution: Fixed Released As: 1.33 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.6351.1572546363447%40Atlassian.JIRA.
[JIRA] (JENKINS-59838) durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/
Title: Message Title Carroll Chiou closed an issue as Incomplete Jenkins / JENKINS-59838 durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/ Change By: Carroll Chiou Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202573.1571383245000.6348.1572546300241%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou updated JENKINS-59907 Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Carroll Chiou Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6333.1572546242884%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou updated JENKINS-59907 Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Carroll Chiou Status: Fixed but Unreleased Resolved Released As: 1.33 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6335.1572546242907%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou reopened an issue Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Carroll Chiou Resolution: Incomplete Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6320.1572546242716%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou closed an issue as Incomplete Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Carroll Chiou Status: In Progress Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6296.1572546181173%40Atlassian.JIRA.
[JIRA] (JENKINS-59838) durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/
Title: Message Title Carroll Chiou commented on JENKINS-59838 Re: durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/ So you can pass in that system property multiple ways. I would recommend passing it in the JVM startup args for however you run Jenkins, or at the script console found in the manage jenkins setting. The JVM startup is where I would recommend you do it. Once that is done, I can't say to where your logs would be, because that would depend on your system and how you installed Jenkins. As for 1.33, i'm not sure why it wouldn't appear in the update center. I know you mentioned that you have issues in 1.30, but if you don't see 1.33, i would recommend downgrading to 1.30. in the plugin manager UI. Could you open a mailing list thread on the jenkinsci-users mailing list for this question? You should add the output once you enable LAUNCH_DIAGNOSTICS, and some details about whether this was working for you previously (i.e. what version of Jenkins you are running, what OS you are using on the Jenkins master and the agent being used by the shell step, etc.). The bug tracker is not the right place for general investigation of issues like this. I am going to close this issue for now, if it looks like there is a bug after you provide more info on the mailing list, we’ll reopen the ticket Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.co
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou started work on JENKINS-59903 Change By: Carroll Chiou Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.5815.1572474542414%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines A Alvarez thanks, that's good to know Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.5717.1572468660936%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines A Alvarez I'm curious, if you are running 1.33, are you passing in the FORCE_BINARY_WRAPPER=true system property? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.5561.1572460500855%40Atlassian.JIRA.
[JIRA] (JENKINS-59838) durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/
Title: Message Title Carroll Chiou edited a comment on JENKINS-59838 Re: durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/ Can you try running your Jenkins with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true? That might help us since the logging right now is not really telling us anything. RIght now it could be anything from a bug in the script, in the environment, or the plugin. Also we are at 1.33 now, so you might try upgrading to that since 1.31 and 1.32 are known to have some issues. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202573.1571383245000.5558.1572460440140%40Atlassian.JIRA.
[JIRA] (JENKINS-59838) durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/
Title: Message Title Carroll Chiou commented on JENKINS-59838 Re: durable-task plugin v1.30 and v1.31 - process aparently never started in /var/lib/jenkins/workspace/ Can you try running your Jenkins with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true? That might help us since the logging right now is not really telling us anything. RIght now it could be anything from a bug in the script, in the environment, or the plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202573.1571383245000..1572460140191%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou commented on JENKINS-59907 Re: sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Version 1.33 has now been released. There is stricter checking on the platforms it runs on. I know not every case has been covered here. The binary is disabled by default so behavior should be simliar, if not same to 1.30 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.4947.1572384540322%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou started work on JENKINS-59907 Change By: Carroll Chiou Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.4931.1572384360662%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou commented on JENKINS-59903 Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container So version 1.33 has now been released. This includes the fix for disabling cache when there are insufficient permissions to access the cache dir. The binary is still disabled by default. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.4886.1572384301092%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou commented on JENKINS-59903 Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container I apologize, what 1.31 did was disable the binary wrapper as default, but it did not resolve the caching issue because the cache dir is stil trying to be created. I am in the process of merging in my current fix (https://github.com/jenkinsci/durable-task-plugin/pull/114) into master. Harald Albers once the fix gets through, those users who do not have permissions to create directories in the build root will have caching disabled. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.4575.1572362581194%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou commented on JENKINS-59903 Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container So a new release 1.32 is out. Until we have a fix out resolving this ticket and, at least, JENKINS-59907, the binary will be disabled by default. Ivan Fernandez CalvoHi Ivan, actually the caching was added as a way to reduce the number of times the master is transmitting the binary over to the agent. What was not taken into account was that the cache directory chosen may not be accessible to the job. A fix is in the works. The binary wrapper itself was added to make the original shell wrapper script more maintainable rather than mystical. There was also an attempt to reduce the issues where the script itself was being terminated for unknown reasons. One of the ways to do this was to use setsid instead of nohup (See JENKINS-25503). The reason the launched script's output is being redirected to a file is so that the output can be transmitted to master in order to display the script's output. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.3829.1572297120979%40Atlassian.JIRA.
[JIRA] (JENKINS-59962) Update of durable task plugin to version 1.31 breaks ARM builds
Title: Message Title Carroll Chiou closed an issue as Duplicate Closing as duplicate of JENKINS-59907 Jenkins / JENKINS-59962 Update of durable task plugin to version 1.31 breaks ARM builds Change By: Carroll Chiou Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou edited a comment on JENKINS-59907 Re: sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Sorry this took so long to address. The binary was not intended to run on non-x86 architectures. Instead, when a non-x86 and non-*NIX architecture is detected, the original shell wrapper was supposed to launch the script. I have a PR up right now that is changing that behavior. I will also update the changelog (that is currently being migrated to github) for this information.The PR can be found here: https://github.com/jenkinsci/durable-task-plugin/pull/114 UPDATE: more work is being done to this PR to handle a few more cases (such as freebsd) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.3652.1572284160362%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou commented on JENKINS-59903 Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container Jonathan B I ran into this issue when I was testing out the fix and running tests on it the very first time. It was solved immediately by running a mvn clean install, so unfortunately I was not able to investigate deeper into the issue as I still can't reproduce it. I think this issue will be solved by reverting to 1.30 and installing again. If that does not solve it, I think it warrants a separate issue. Jesper Andersson I don't think there has been anything official on using caches on the agent. Not many plugins use caching, but i think is something that we should explore further since I think most people want to reduce the workload of the masters. Hari Dara Yes, there should be more error handling involved. I am looking to add that in. The tricky part is the script is supposed to be launched as a fire and forget, this includes the original shell wrapper as well. But of course, it's one thing if your shell fails to launch vs this binary. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.3608.1572284041085%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou commented on JENKINS-59903 Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container So, apologies for this taking so long to address. There is currently a fix in the works right now for this issue and JENKINS-59907 as well. I will also update the changelog that is currently being migrated to github. Caching will be disabled when the cache directory is unavailable to the agent. The PR can be found here: https://github.com/jenkinsci/durable-task-plugin/pull/114 ci.jenkins.io is quite unstable right now. Hopefully things will get better sooner. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.2912.1572249361959%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou commented on JENKINS-59907 Re: sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Sorry this took so long to address. The binary was not intended to run on non-x86 architectures. Instead, when a non-x86 and non-*NIX architecture is detected, the original shell wrapper was supposed to launch the script. I have a PR up right now that is changing that behavior. I will also update the changelog (that is currently being migrated to github) for this information. The PR can be found here: https://github.com/jenkinsci/durable-task-plugin/pull/114 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.2914.1572249361988%40Atlassian.JIRA.
[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client
Title: Message Title Carroll Chiou assigned an issue to Unassigned Jenkins / JENKINS-59906 durable-task plugin v1.31 fails to execute shell commands on swarm client Change By: Carroll Chiou Assignee: Carroll Chiou Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202656.1571852611000.2785.1572238270250%40Atlassian.JIRA.
[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client
Title: Message Title Carroll Chiou assigned an issue to Carroll Chiou Jenkins / JENKINS-59906 durable-task plugin v1.31 fails to execute shell commands on swarm client Change By: Carroll Chiou Assignee: Carroll Chiou Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202656.1571852611000.2778.1572238140274%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Carroll Chiou assigned an issue to Carroll Chiou Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Carroll Chiou Assignee: Carroll Chiou Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.2768.1572233700400%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou assigned an issue to Carroll Chiou Jenkins / JENKINS-59903 durable-task v1.31 breaks sh steps in pipeline when running in a Docker container Change By: Carroll Chiou Assignee: Carroll Chiou Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.2722.1572219061069%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou edited a comment on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines The sleep 3 process was introduced when the heartbeat check feature was added in version 1.16 of durable-task, which translates to 2.18 of workflow-durable-task-step, which translates to 2.27 of workflow-job.Unless I missed a comment, it looks like the pipeline behaves as expected outside of "Terminated sleep 3" line.At least in [~parogui]’s [example|https://issues.jenkins-ci.org/browse/JENKINS-55308?focusedCommentId=377961&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-377961], this might be a race condition between the sleep 3 process and when the script completes. Like [~dnusbaum] [mentioned earlier|https://issues.jenkins-ci.org/browse/JENKINS-55308?focusedCommentId=362789&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-362789], the sleep 3 process is used to touch the output log file to show the script is still alive. However, when the script completes, it will write to a separate result file. A watcher service is checking for that result file every 100ms. Once that result file is found, results are transmitted and everything related to that specific step’s workspace is purged. It might be possible that the output file gets cleaned up right after the sleep 3 process checks if the file still exists, but before it gets touched again?There is a new release of durable-task (1.31) that removes the sleep 3 process so this line won't pop up anymore. Update: I have not been able to reproduce this issue, so I can't say for certain if this issue is resolved. Technically, it should, but it could be possible that the new version just changes the behavior of this bug. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou started work on JENKINS-55308 Change By: Carroll Chiou Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.525.1571941503719%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou assigned an issue to Carroll Chiou Jenkins / JENKINS-55308 intermittent "terminated" messages using sh in Pipelines Change By: Carroll Chiou Assignee: Devin Nusbaum Carroll Chiou Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.486.1571941321036%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou edited a comment on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines The sleep 3 process was introduced when the heartbeat check feature was added in version 1.16 of durable-task, which translates to 2.18 of workflow-durable-task-step, which translates to 2.27 of workflow-job.Unless I missed a comment, it looks like the pipeline behaves as expected outside of "Terminated sleep 3" line.At least in [~parogui]’s [example|https://issues.jenkins-ci.org/browse/JENKINS-55308?focusedCommentId=377961&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-377961], this might be a race condition between the sleep 3 process and when the script completes. Like [~dnusbaum] [mentioned earlier|https://issues.jenkins-ci.org/browse/JENKINS-55308?focusedCommentId=362789&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-362789], the sleep 3 process is used to touch the output log file to show the script is still alive. However, when the script completes, it will write to a separate result file. A watcher service is checking for that result file every 100ms. Once that result file is found, results are transmitted and everything related to that specific step’s workspace is purged. It might be possible that the output file gets cleaned up right after the sleep 3 process checks if the file still exists, but before it gets touched again?There will be is a new release of durable-task (1.31) that will remove removes the sleep 3 process so this line won't pop up anymore. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -
[JIRA] (JENKINS-25503) Use setsid instead of nohup
Title: Message Title Carroll Chiou updated JENKINS-25503 Shell wrapper script has now been replaced by pre-compiled golang binaries (for Unix and Darwin). The binary allows the script to have its own session id and removes some polling overhead. This should increase the survivability of long-running scripts when jenkins terminates unexpectedly. This does not change the survivability of the script when the underlying environment decides to terminate processes due to things like low memory. Note: Outside of *NIX systems, the behavior is unchanged. The binary itself is ~2.5MB per binary. There are 4 pre-compiled binaries (32 and 64bit versions for unix and darwin) while the memory footprint is ~800KB heavier than the shell wrapper. Here is a high-level breakdown of the memory footprint: Original version: two wrapper shell processes that are spawned, each process between 610-640KB a single 548KB sleep process used to poll the log output file Go binary version: a single golang binary ~2560KB Jenkins / JENKINS-25503 Use setsid instead of nohup Change By: Carroll Chiou Status: In Review Fixed but Unreleased Resolution: Fixed Released As: durable-task 1.31 Add Comment
[JIRA] (JENKINS-25503) Use setsid instead of nohup
Title: Message Title Carroll Chiou updated JENKINS-25503 Jenkins / JENKINS-25503 Use setsid instead of nohup Change By: Carroll Chiou Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159068.1415403303000.13474.1571775601726%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines The sleep 3 process was introduced when the heartbeat check feature was added in version 1.16 of durable-task, which translates to 2.18 of workflow-durable-task-step, which translates to 2.27 of workflow-job. Unless I missed a comment, it looks like the pipeline behaves as expected outside of "Terminated sleep 3" line. At least in Pablo Rodriguez’s example, this might be a race condition between the sleep 3 process and when the script completes. Like Devin Nusbaum mentioned earlier, the sleep 3 process is used to touch the output log file to show the script is still alive. However, when the script completes, it will write to a separate result file. A watcher service is checking for that result file every 100ms. Once that result file is found, results are transmitted and everything related to that specific step’s workspace is purged. It might be possible that the output file gets cleaned up right after the sleep 3 process checks if the file still exists, but before it gets touched again? There will be a new release of durable-task that will remove the sleep 3 process so this line won't pop up anymore. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title
Carroll Chiou edited a comment on JENKINS-58656
Re: Wrapper process leaves zombie when no init process present
Yes, just to clarify, I ran my Jenkinsfile on a Jenkins instance that was deployed to GKE. The Jenkinsfile has two stages to it, with each stage running a different pod template. The only difference between the two pod templates is thatI add the ` {{ shareProcessNamespace: true ` }} to the last stage. You have to look a bit carefully, but in the ` {{ ps output ` }} for the first stage, you will see a zombie process, whereas in the second stage, there is no zombie process.Now this instance is running my latest version of `durable-task` from [PR-106|https://github.com/jenkinsci/durable-task-plugin/pull/106]. The behavior is still the same with the latest version on `master`I only need to run ` {{ sh ` }} once and wait a bit to pull up a zombie instance. `Durable {{durable -task ` }} is guaranteed to create a zombie every time it is executed due to the background process requirement. This only happens within the container itself, so once the container goes away, so do the zombies. My understanding of zombie processes is that the only resource they're consuming is the entry in the process table. So I guess if you have a long running container that's doing a serious amount of shell steps then you can run into trouble? For reference, I looked into ` {{ /proc/sys/kernel/pid_max ` }} for the ` {{ jenkins/jnlp-slave ` }} image and got ` {{ 99,999 ` }} . Apparently on 32 bit systems {{ pid_max }} can be configured up to {{ >4 million (2^22) }} entries. And this is all for just one container.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.g
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title
Carroll Chiou edited a comment on JENKINS-58656
Re: Wrapper process leaves zombie when no init process present
Yes, just to clarify, I ran my Jenkinsfile on a Jenkins instance that was deployed to GKE. The Jenkinsfile has two stages to it, with each stage running a different pod template. The only difference between the two pod templates is thatI add the {{shareProcessNamespace: true}} to the last stage. You have to look a bit carefully, but in the {{ps output}} for the first stage, you will see a zombie process, whereas in the second stage, there is no zombie process.Now this instance is running my latest version of `durable-task` from [PR-106|https://github.com/jenkinsci/durable-task-plugin/pull/106]. The I can also confirm that the behavior is still the same with the latest version on `master`I only need to run {{sh}} once and wait a bit to pull up a zombie instance. {{durable-task}} is guaranteed to create a zombie every time it is executed due to the background process requirement. This only happens within the container itself, so once the container goes away, so do the zombies. My understanding of zombie processes is that the only resource they're consuming is the entry in the process table. So I guess if you have a long running container that's doing a serious amount of shell steps then you can run into trouble? For reference, I looked into {{/proc/sys/kernel/pid_max}} for the {{jenkins/jnlp-slave}} image and got {{99,999}}. Apparently on 32 bit systems {{pid_max}} can be configured up to {{>4 million (2^22)}} entries. And this is all for just one container.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200936
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Carroll Chiou commented on JENKINS-58656 Re: Wrapper process leaves zombie when no init process present Yes, just to clarify, I ran my Jenkinsfile on a Jenkins instance that was deployed to GKE. The Jenkinsfile has two stages to it, with each stage running a different pod template. The only difference between the two pod templates is thatI add the `shareProcessNamespace: true` to the last stage. You have to look a bit carefully, but in the `ps output` for the first stage, you will see a zombie process, whereas in the second stage, there is no zombie process. Now this instance is running my latest version of `durable-task` from PR-106. The behavior is still the same with the latest version on `master` I only need to run `sh` once and wait a bit to pull up a zombie instance. `Durable-task` is guaranteed to create a zombie every time it is executed due to the background process requirement. This only happens within the container itself, so once the container goes away, so do the zombies. My understanding of zombie processes is that the only resource they're consuming is the entry in the process table. So I guess if you have a long running container that's doing a serious amount of shell steps then you can run into trouble? For reference, I looked into `/proc/sys/kernel/pid_max` for the `jenkins/jnlp-slave` image and got `99,999`. Apparently on 32 bit systems pid_max can be configured up to >4 million (2^22) entries. And this is all for just one container. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200936.1564038973000.8958.1566592320288%40Atlassian.JIRA.
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Carroll Chiou edited a comment on JENKINS-58656 Re: Wrapper process leaves zombie when no init process present It looks like if you enable pid namespace sharing, the pause container will handle zombie reaping (kubernetes 1.7+ and docker 1.13.1+). Otherwise you will have to have each container handle the zombie reaping independently.https://www.ianlewis.org/en/almighty-pause-containerhttps://github.com/kubernetes/community/blob/master/contributors/design-proposals/node/pod-pid-namespace.md Update: ran a quick test to confirm this does work:- [Jenkinsfile|https://gist.github.com/car-roll/4471dc9231abeb1db1271ad349706bcb]- [Console output|https://gist.github.com/car-roll/0dc1f124090ebee569cce4af17db6d1b] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200936.1564038973000.8500.1566553440217%40Atlassian.JIRA.
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Carroll Chiou commented on JENKINS-58656 Re: Wrapper process leaves zombie when no init process present It looks like if you enable pid namespace sharing, the pause container will handle zombie reaping (kubernetes 1.7+ and docker 1.13.1+). Otherwise you will have to have each container handle the zombie reaping independently. https://www.ianlewis.org/en/almighty-pause-container https://github.com/kubernetes/community/blob/master/contributors/design-proposals/node/pod-pid-namespace.md Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200936.1564038973000.8063.1565028480181%40Atlassian.JIRA.
[JIRA] (JENKINS-33217) DescribableHelper does not detect stray parameters
Title: Message Title Carroll Chiou updated JENKINS-33217 A fix for this issue has been released in version 1.20 of structs Jenkins / JENKINS-33217 DescribableHelper does not detect stray parameters Change By: Carroll Chiou Status: In Review Resolved Resolution: Fixed Released As: structs 1.20 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168598.1456760629000.3443.1564425000342%40Atlassian.JIRA.
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title
Carroll Chiou updated an issue
Jenkins / JENKINS-58656
Wrapper process leaves zombie when no init process present
Change By:
Carroll Chiou
The merge of [PR-98|https://github.com/jenkinsci/durable-task-plugin/pull/98] moved the wrapper process to the background but to allow the launching process to quickly exit. However , as a result, zombies it that very act will orphan the wrapper process . This is only a problem in environments where there is no {{init}} process (e.g. docker containers that are run with no {{--init}} flag). Unit tests did not discover this bug due to a race condition of when the last {{ps}} was called and when the wrapper process exited. If another {{ps}} is called after the test detects that the script as finished running, the zombie state of the wrapper process is revealed.I'm not sure how much of an issue this really is as there are numerous solutions on enabling zombie-reaping for containers, but as there is an explicit check for zombies in the unit tests, it seemed worth mentioning.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on th
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Carroll Chiou created an issue Jenkins / JENKINS-58656 Wrapper process leaves zombie when no init process present Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-07-25 07:16 Environment: Running version 1.30-rc422.f179f78e479f Priority: Minor Reporter: Carroll Chiou The merge of PR-98 moved the wrapper process to the background but, as a result, zombies it. This is only a problem in environments where there is no init process (e.g. docker containers that are run with no --init flag). Unit tests did not discover this bug due to a race condition of when the last ps was called and when the wrapper process exited. If another ps is called after the test detects that the script as finished running, the zombie state of the wrapper process is revealed. I'm not sure how much of an issue this really is as there are numerous solutions on enabling zombie-reaping for containers, but as there is an explicit check for zombies in the unit tests, it seemed worth mentioning. Add
[JIRA] (JENKINS-33217) DescribableHelper does not detect stray parameters
Title: Message Title Carroll Chiou assigned an issue to Carroll Chiou Jenkins / JENKINS-33217 DescribableHelper does not detect stray parameters Change By: Carroll Chiou Assignee: Jesse Glick Carroll Chiou Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168598.1456760629000.3139.1562347920254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52272) Bitbucket branch source plugin doesn't update correctly the list of repositories
Title: Message Title Carroll Chiou edited a comment on JENKINS-52272 Re: Bitbucket branch source plugin doesn't update correctly the list of repositories In the Unable to reproduce bug with current behavior on Master, the master. Bitbucket cache is has been disabled , so the list of repos is updated correctly by default since 2 . 2.1. To reproduce the problem and verify the correct caching behavior, the following was done:# Enable the cache of Bitbucket endpoints in global config# Create a new multibranch project and add Bitbucket branch source # * * Confirmed the list of repos is showing correctly# Create a new Bitbucket repo# Create another multibranch project and add Bitbucket branch source # * * Confirmed that the newest Bitbucket repo was *not* show in the repo list# Disabled cache of Bitbucket endpoints# Go back to the lastest multibranch project and add Bitbucket branch source # * * Confirmed that the newest Bitbucket repo is showing and the list of repos is correct # Similar verification was also done by waiting for the Bitbucket cache period to expire and reloading the Bitbucket repositories list. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52272) Bitbucket branch source plugin doesn't update correctly the list of repositories
Title: Message Title Carroll Chiou updated JENKINS-52272 Cache is disabled by default in 2.2.12 Jenkins / JENKINS-52272 Bitbucket branch source plugin doesn't update correctly the list of repositories Change By: Carroll Chiou Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52272) Bitbucket branch source plugin doesn't update correctly the list of repositories
Title: Message Title Carroll Chiou updated JENKINS-52272 Jenkins / JENKINS-52272 Bitbucket branch source plugin doesn't update correctly the list of repositories Change By: Carroll Chiou Resolution: Fixed Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52272) Bitbucket branch source plugin doesn't update correctly the list of repositories
Title: Message Title Carroll Chiou resolved as Fixed In the current behavior on Master, the Bitbucket cache is disabled, so the list of repos is updated correctly. To reproduce the problem and verify the correct behavior, the following was done: Enable the cache of Bitbucket endpoints in global config Create a new multibranch project and add Bitbucket branch source Confirmed the list of repos is showing correctly Create a new Bitbucket repo Create another multibranch project and add Bitbucket branch source Confirmed that the newest Bitbucket repo was not show in the repo list Disabled cache of Bitbucket endpoints Go back to the lastest multibranch project and add Bitbucket branch source Confirmed that the newest Bitbucket repo is showing and the list of repos is correct Jenkins / JENKINS-52272 Bitbucket branch source plugin doesn't update correctly the list of repositories Change By: Carroll Chiou Status: In Progress Resolved Resolution: Fixed
[JIRA] (JENKINS-52272) Bitbucket branch source plugin doesn't update correctly the list of repositories
Title: Message Title Carroll Chiou assigned an issue to Carroll Chiou Jenkins / JENKINS-52272 Bitbucket branch source plugin doesn't update correctly the list of repositories Change By: Carroll Chiou Assignee: Carroll Chiou Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52272) Bitbucket branch source plugin doesn't update correctly the list of repositories
Title: Message Title Carroll Chiou started work on JENKINS-52272 Change By: Carroll Chiou Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54051) GitHub-Branch-Source plugin 2.3.5 Security Update causing error in adding GitHub Enterprise Servers
Title: Message Title Carroll Chiou updated JENKINS-54051 Issue was with the checkMethod="post" being in the wrong field of a config jelly file Jenkins / JENKINS-54051 GitHub-Branch-Source plugin 2.3.5 Security Update causing error in adding GitHub Enterprise Servers Change By: Carroll Chiou Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54051) GitHub-Branch-Source plugin 2.3.5 Security Update causing error in adding GitHub Enterprise Servers
Title: Message Title Carroll Chiou updated JENKINS-54051 Jenkins / JENKINS-54051 GitHub-Branch-Source plugin 2.3.5 Security Update causing error in adding GitHub Enterprise Servers Change By: Carroll Chiou Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54051) GitHub-Branch-Source plugin 2.3.5 Security Update causing error in adding GitHub Enterprise Servers
Title: Message Title Carroll Chiou started work on JENKINS-54051 Change By: Carroll Chiou Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54051) GitHub-Branch-Source plugin 2.3.5 Security Update causing error in adding GitHub Enterprise Servers
Title: Message Title Carroll Chiou assigned an issue to Carroll Chiou Jenkins / JENKINS-54051 GitHub-Branch-Source plugin 2.3.5 Security Update causing error in adding GitHub Enterprise Servers Change By: Carroll Chiou Assignee: Carroll Chiou Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
