[JIRA] (JENKINS-52859) ps: unrecognized option: p
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-52859 ps: unrecognized option: p Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate 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-52859) ps: unrecognized option: p
Title: Message Title Patrick Baber commented on JENKINS-52859 Re: ps: unrecognized option: p I had the same problem, but I first saw the jobs aborted with a message like this: wrapper script does not seem to be touching the log file in /var/_home/workspace/project-BBCPYWAXGTF745UL4PB4M3MPJPPB3QBHBKQGDBMMUI4RXBZRYJCQ@tmp/durable-ebb51810 (JENKINS-48300: if on a laggy filesystem, consider -Dorg.ci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300) script returned exit code -1 With that I found a the wrong hint on Stack Overflow: https://stackoverflow.com/questions/50067372/where-to-set-dorg-jenkinsci-plugins-durabletask-bourneshellscript-heartbeat-che Only the downgrade of the Durable Task plugin to version 1.22 helps me. Just saying… 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-52859) ps: unrecognized option: p
Title: Message Title yan-hong wang commented on JENKINS-52859 Re: ps: unrecognized option: p Totally same with Martin Bornhold. In my case, now I downgrade to use 'kubernetes:1.10.2' because 'kubernetes:1.11.0' will lead 'Durable Task' upgrade to 1.23. 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-52859) ps: unrecognized option: p
Title: Message Title Charlie Stocker edited a comment on JENKINS-52859 Re: ps: unrecognized option: p [~bgras]is correct. Here is the git blame that introduced this bug:[https://github.com/jenkinsci/durable-task-plugin/blame/master/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java#L143]This affects any container that uses BusyBox instead of GNU Coreutils procps . BusyBox's ps is quite limited and doesn't support any kind of filtering except for the column output.As the command is already running a grep to check for the existence of the watched PID in the ps output, it's redundant to also ask ps to only show us that PID so the -p parameter could be dropped to maintain compatibility with busybox 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-52859) ps: unrecognized option: p
Title: Message Title Charlie Stocker commented on JENKINS-52859 Re: ps: unrecognized option: p Benjamin Grasis correct. Here is the git blame that introduced this bug: https://github.com/jenkinsci/durable-task-plugin/blame/master/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java#L143 This affects any container that uses BusyBox instead of GNU Coreutils. BusyBox's ps is quite limited and doesn't support any kind of filtering except for the column output. As the command is already running a grep to check for the existence of the watched PID in the ps output, it's redundant to also ask ps to only show us that PID so the -p parameter could be dropped to maintain compatibility with busybox 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-52859) ps: unrecognized option: p
Title: Message Title Benjamin Gras updated an issue Jenkins / JENKINS-52859 ps: unrecognized option: p Change By: Benjamin Gras Environment: Jenkins Alpine LTS Docker image durable-task-plugin 1.23 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-52859) ps: unrecognized option: p
Title: Message Title Benjamin Gras updated an issue Jenkins / JENKINS-52859 ps: unrecognized option: p Change By: Benjamin Gras Component/s: durable-task-plugin 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-52859) ps: unrecognized option: p
Title: Message Title Martin Bornhold commented on JENKINS-52859 Re: ps: unrecognized option: p Hi, this bug also hit me and I am also running it on Alpine based docker images. For me it looks like this bug leads to not propagating the correct data from the processes to the Durable Task plugin beacuse it kills long running processes which are definitely not stuck and producing output on the console. This is only my assumption, did not investiage on it. Downgrading from 1.23 -> 1.22 solves the issue for me but a fix would be greatly appreciated I am unsing Jenkins 2.121.2 in Kubernetes (docker). 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-52859) ps: unrecognized option: p
Title: Message Title Benjamin Gras commented on JENKINS-52859 Re: ps: unrecognized option: p It looks like it might come from the latest version for the "Durable Task" plugin. I have the same problem in 1.23, and I did not have it in 1.22 (and it looks like it's a big update). Could you check on your side and update the component if it's the same for you ? I'm running Jenkins 2.135 in docker. 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-52859) ps: unrecognized option: p
Title: Message Title Taras Postument created an issue Jenkins / JENKINS-52859 ps: unrecognized option: p Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin, pipeline Created: 2018-08-02 15:37 Environment: Jenkins Alpine LTS Docker image Priority: Minor Reporter: Taras Postument Hello. I'm using the Blueocean and Pipelines on Alpine linux and started seeing next error on each Pipeline SH step: [Pipeline] sh[decline_cookies_policy-testing-job] Running shell script ps: unrecognized option: p BusyBox v1.28.4 (2018-05-30 10:45:57 UTC) multi-call binary. Usage: ps [-o COL1,COL2=HEADER] Show list of processes -o COL1,COL2=HEADER Select columns for display + echo hello world[Pipeline] } Looks like plugin tries to call `ps` with unsuported for Alpine parameters on each sh step. Add Comment
