[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-33846) Restart pipeline from specific stage, after failure
Title: Message Title Katherine Morgan edited a comment on JENKINS-33846 Re: Restart pipeline from specific stage, after failure I really really really want this feature. And it is absolutely going to stop me from using the pipeline functionality. I just spent a full day implementing my build and deployment process with the pipeline functionality. I have builds that progress through these stages: BUILD > DEV > STAGE > INTEG > PREPROD > PROD. I'm using the 'waiting for input' feature to capture human approval to progress the deployment to the next environment. In testing it, I found that the pipelines would fill my 'build executor status' list whilst they were 'waiting for approval', and would block jenkins from doing any more work. Just not usable. If the 'restart a stage' feature existed, I could then deploy any pipeline to any environment, achieving build progression and rollback.*UPDATE:* I've since learnt that I need to move my input to outside of a node, this resolves my blocked executors. 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-33846) Restart pipeline from specific stage, after failure
Title: Message Title Katherine Morgan commented on JENKINS-33846 Re: Restart pipeline from specific stage, after failure I really really really want this feature. And it is absolutely going to stop me from using the pipeline functionality. I just spent a full day implementing my build and deployment process with the pipeline functionality. I have builds that progress through these stages: BUILD > DEV > STAGE > INTEG > PREPROD > PROD. I'm using the 'waiting for input' feature to capture human approval to progress the deployment to the next environment. In testing it, I found that the pipelines would fill my 'build executor status' list whilst they were 'waiting for approval', and would block jenkins from doing any more work. Just not usable. If the 'restart a stage' feature existed, I could then deploy any pipeline to any environment, achieving build progression and rollback. 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] [build-pipeline-plugin] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Katherine Morgan commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job Still a problem for: Jenkins 1.654 Build Pipeline plugin 1.5.2 Parameterized Trigger plugin 2.30 Tested with Chrome 49.0.2623.87 m, and Firefox 44.0.2. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.