[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Nancy Robertson commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once I like Uliul Carpatin's solution that does not break existing code. It or a variant thereof could also include stdErr... 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.183003.149756330.11578.1586956501969%40Atlassian.JIRA.
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Nancy Robertson commented on JENKINS-57347 Re: Performance degradation running pipeline step sh on remote agents Ok, I will try that now, where do I get the private key? 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.199122.1557175676000.395.1560445020093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Nancy Robertson commented on JENKINS-57347 Re: Performance degradation running pipeline step sh on remote agents Ivan Fernandez Calvo I have been trying to use your docker compose setup to reproduce your success, but I am having a bit of trouble. On the VM where I do this, port 22 is already used by a ssh server. So I added a couple of lines in the docker compose file to change the port to 8022 and when I start the jenkins and change the port (and the host name so it will reach my VM) in the ssh-agent node definition, it says it cannot connect with the key that is stored in the credentials. 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.199122.1557175676000.356.1560441480105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Nancy Robertson commented on JENKINS-57347 Re: Performance degradation running pipeline step sh on remote agents Ivan Fernandez Calvo I tried setting the property, then disconnected and reconnected my agent. It makes no measurable difference. 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.199122.1557175676000.20250.1557244860264%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Nancy Robertson created an issue Jenkins / JENKINS-57347 Performance degradation running pipeline step sh on remote agents Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: issue-ssh-slaves-perf.groovy Components: ssh-slaves-plugin Created: 2019-05-06 20:47 Environment: Jenkins ver. 2.150.2 ssh-slaves plugin version 1.27 to 1.29.4 Priority: Minor Reporter: Nancy Robertson I noticed a severe performance degradation in the execution of the pipeline sh step when the agent is connected via the ssh-slaves plugin. I performed extra testing on a standalone jenkins installed from docker image jenkins/jenkins:lts with a number of different versions of the ssh-slaves plugin. Attached is the Jenkinsfile I used to test this. With 10 iterations of the sh step, versions 1.26 takes 14-15 seconds while version 1.27 takes 24-27 seconds. That is without taking into account the first build after the agent has started which always takes longer (22 seconds in 1.26 and 40 seconds in 1.27) I have also tried "Launch agent via execution of a command on the master" which performs in a way comparable to the ssh-slaves plugin in version before 1.27. The only workaround I found is to keep the ssh-slaves plugin at version 1.26.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title Nancy Robertson commented on JENKINS-45579 Re: Step to set stage or parallel status Nofar Bluestein - Many thanks for looking into this. Your proposal sounds good. I am particularly interested in the handling of the unstable condition. Our pipelines are mostly scripted, and we have been using the error() function to mark failed stages, but it would help to be able to mark stages as unstable and keep going. Does your current plan include the addition of an unstable() step? 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Nancy Robertson commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should I have a somewhat related question: Is there an API to access the results of the various stages in a pipeline? I have been playing tricks like setting a variable with the name of the current stage when a stage starts and checking its contents in the post for the pipeline to report which stage failed and would like to have a cleaner solution to work with what is already in place... 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] [disk-usage] (JENKINS-22345) disk-usage-plugin causes jobs to hang at the end for 5min
Nancy Robertson edited a comment on JENKINS-22345 disk-usage-plugin causes jobs to hang at the end for 5min I have encountered this issue on my Jenkins installation with a subset of the jobs. The jobs that have this problem are the ones that have a Custom Workspace defined. After the job finishes, the jenkins process on the master starts using a lot of CPU while the Disk Usage plugin is trying to estimate the size of the workspace on the slave. While this is happening, the build history for the job shows that it has finished, but the job is still shown in the Build Executor Status and the console log for the build does not show the expected last statement of "Finished: SUCCESS". This goes on for 5 minutes, which happens to match the configured value of the timeout for calculating the size of the workspace on slaves. Not sure if this matters, but our jobs are of type: "free-style software project" and the version of Jenkins we use is 1.566 We had version 0.23 of the disk usage plugin, the problem went away by uninstalling the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [disk-usage] (JENKINS-22345) disk-usage-plugin causes jobs to hang at the end for 5min
Nancy Robertson commented on JENKINS-22345 disk-usage-plugin causes jobs to hang at the end for 5min I have encountered this issue on my Jenkins installation with a subset of the jobs. The jobs that have this problem are the ones that have a Custom Workspace defined. After the job finishes, the jenkins process on the master starts using a lot of CPU while the Disk Usage plugin is trying to estimate the size of the workspace on the slave. While this is happening, the build history for the job shows that it has finished, but the job is still shown in the Build Executor Status and the console log for the build does not show the expected last statement of "Finished: SUCCESS". This goes on for 5 minutes, which happens to match the configured value of the timeout for calculating the size of the workspace on slaves. Not sure if this matters, but our jobs are of type: "free-style software project" and the version of Jenkins we use is 1.566 We had version 0.23 of the disk usage plugin, the problem went away by uninstalling the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
