[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Jesse Glick commented on JENKINS-37515 Re: pipeline input blocks the executor how to batch delete old job instances See https://github.com/jenkinsci/workflow-aggregator-plugin/tree/master/demo for milestone usage. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Jesse Glick resolved as Not A Defect AFAIK that syntax in Declarative would work, but if it does not, that would be a bug report for pipeline-model-definition-plugin. Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Jesse Glick Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Markus Till commented on JENKINS-37515 Re: pipeline input blocks the executor Hi, I tried to create a job like this pipeline { *agent none* stages { stage('Build') { agent any steps { echo 'This is a minimal pipeline.' } } stage('Deploy') { *agent none* steps { input message: 'test', ok: 'test', submitterParameter: 'test' } } } } I'll hoped that agent none for the deploy step would prevent me from a blocked agent but it doesn't I think there should be a way to create a pipeline inupt without blocking a whole worker thread. Are there any plans to do so? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Attachment: build_history_with_more_builds_as_log_rotation.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Attachment: log_rotation.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber commented on JENKINS-37515 Re: pipeline input blocks the executor This is a little bit confusing: the build history shows all the jobs running until you proceed or abort any job instande. Additional old "running" jobs are not deleted by log rotation. So how to batch delete old job instances or timeout these? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Katherine Morgan commented on JENKINS-37515 Re: pipeline input blocks the executor Hi @tkleiber, Your screenshot shows the job in the build history for your 'PipelineTest' job, not the 'Build Executor Status' list which is on the main jenkins page, see my screenshot. When I made the change suggested by Jesse, the jobs do drop out of the executor list. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Katherine Morgan updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Katherine Morgan Attachment: jenkins-build-executor.PNG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber reopened an issue See my last comment. Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber edited a comment on JENKINS-37515 Re: pipeline input blocks the executor In which version do you have tested this, does not work in 2.7.2 here with following example !20160912_070739.png|thumbnail! : {{ node { stage 'Build after Commit'}stage 'Deploy against developement'input 'Are you sure?' }} Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber edited a comment on JENKINS-37515 Re: pipeline input blocks the executor In which version do you have tested this, does not work in 2.7.2 here with following example !20160912_070739.png|thumbnail! :{ { node { stage 'Build after Commit'}stage 'Deploy against developement'input 'Are you sure?'} } Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber commented on JENKINS-37515 Re: pipeline input blocks the executor In which version do you have tested this, does not work in 2.7.2 here with following example : node { stage 'Build after Commit' } stage 'Deploy against developement' input 'Are you sure?' Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Attachment: 20160912_070739.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Katherine Morgan commented on JENKINS-37515 Re: pipeline input blocks the executor Thanks for the tip Jesse Glick, that resolved it for me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Jesse Glick resolved as Not A Defect If you need to release the executor, put input outside node. If you need to keep some files from the workspace, stash them before you leave. Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Kanstantsin Shautsou commented on JENKINS-37515 Re: pipeline input blocks the executor I think the issue will be with workspace. Executor will hold workspace that may be needed for continuation after input. Some adittional non-blocking input maybe needs to be created? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Issue Type: Bug Assignee: Oleg Nenashev Components: pipeline-_unsorted Created: 2016/Aug/18 1:12 PM Environment: Jenkins LTS 2.72 rpm on SLES 11 SP 4 Priority: Major Reporter: Torsten Kleiber When using an input step in pipeline, the executor is blocked until you proceed or abort the input step. We have here the case that the code is build whenever it is changed in the scm via polling. Only a small number of the builds going to development, staging and production. As the executor is blocked, the maximum number of executors is reached in short time. The build pipeline plugin instead use an executor for every job it contains. Is it possible to break end the executor when input step is reached and restart after proceed answer? Add Comment