[JIRA] (JENKINS-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick commented on JENKINS-33761 Re: Ability to disable "resume" build. FTR I have recently also come across the bug of jobs not restarting This was filed separately and a fix released. 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-33761) Ability to disable "resume" build.
Title: Message Title R N commented on JENKINS-33761 Re: Ability to disable "resume" build. WRT JENKINS-41916, It would be good if the Resume build option is disabled as it doesn't respect Security. 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-33761) Ability to disable "resume" build.
Title: Message Title
Matthew Hall commented on JENKINS-33761
Re: Ability to disable "resume" build.
Hello, I have recently also come across the bug of jobs not restarting, I can also provide a testcase to help with investigation, three jobs are required: Job 1 will trigger job_40_sec and job_50_sec in parallel If jenkins restarts or is killed when job_40_sec and job_50_sec are both running, then, when Jenkins comes back online only one of the jobs is restarted whilst the other hangs indefinitely Please let me know if you need any more information or if this is the wrong place for this information Pipeline scripts: Job 1
Map parallel_jobs = ['branch_1': {build job: 'job_50_sec'},
'branch_2': {build job: 'job_40_sec'}]
parallel parallel_jobs
job_40_sec
node { sleep(40) }
job_50_sec
node { sleep(50) }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33761) Ability to disable "resume" build.
Title: Message Title
Nenad Miksa edited a comment on JENKINS-33761
Re: Ability to disable "resume" build.
[~jglick], unfortunately the bug is not deterministic - usually after restart jobs just hang, but can be killed (with kill of course, rarely works with stop).The shell script which hanged in a way that after resume job could not be killed at all is this: {code:java} sh "curl -s -X POST https://bitbucket.org/site/oauth2/access_token -u \"${getBitbucketOAuthKey()}:${getBitbucketOAuthSecret()}\" -d grant_type=client_credentials | jsawk 'return this.access_token' | tr -d \"\\n\" > accessToken.txt" {code} Script obtains access token for BitBucket API so it can be used later for notifying commit statuses and approving pull request - something that bitbucket branch source plugin does not support (later they added support for that, but it is not configurable to give flexibility we need). I cannot guarantee you that this will trigger the bug, since this shell script is executed for every build we have and only 3 jobs (out of dozens daily) have been executing this script at the time of jenkins restart, which caused them to lock in a way that even kill didn't work.However, it would be better to just fix resuming of jobs - since the original bug report, I have seen much improvements in this field (unix shell scripts now rarely hang after resume, but windows batch script almost always do). As I said, the most problematic are windows batch scripts running cmake-base build of visual studio c++ projects (cmake is used to create visual studio solution and then 'cmake --build . --config Release .' is used to invoke MSBuild builder to build the project). When restart is triggered (on master node, which is linux box) while this build is executing on windows slave, first this batch script is terminated (I guess with some kind of interrupt signal) which causes MSVC to report build as failed (MSVC reports cancelled builds as failures) and after restart this batch script is resumed, but instead of either new build with MSBuild or new call to entire batch script (which should build the project correctly) or continuing with next batch script which is followed after the one which performs the build (which actually collects test results and stashes them so later master node can utilize XUnit publisher plugin to publish test results), the job simply hangs and does nothing indefinitely (until someone logs in and kills it, because stop command is also ignored).
Add Comment
[JIRA] (JENKINS-33761) Ability to disable "resume" build.
Title: Message Title
Nenad Miksa commented on JENKINS-33761
Re: Ability to disable "resume" build.
Jesse Glick, unfortunately the bug is not deterministic - usually after restart jobs just hang, but can be killed (with kill of course, rarely works with stop). The shell script which hanged in a way that after resume job could not be killed at all is this: sh "curl -s -X POST https://bitbucket.org/site/oauth2/access_token -u \"$ {getBitbucketOAuthKey()} :$ {getBitbucketOAuthSecret()} \" -d grant_type=client_credentials | jsawk 'return this.access_token' | tr -d \"\\n\" > accessToken.txt" Script obtains access token for BitBucket API so it can be used later for notifying commit statuses and approving pull request - something that bitbucket branch source plugin does not support (later they added support for that, but it is not configurable to give flexibility we need). I cannot guarantee you that this will trigger the bug, since this shell script is executed for every build we have and only 3 jobs (out of dozens daily) have been executing this script at the time of jenkins restart, which caused them to lock in a way that even kill didn't work. However, it would be better to just fix resuming of jobs - since the original bug report, I have seen much improvements in this field (unix shell scripts now rarely hang after resume, but windows batch script almost always do). As I said, the most problematic are windows batch scripts running cmake-base build of visual studio c++ projects (cmake is used to create visual studio solution and then 'cmake --build . --config Release .' is used to invoke MSBuild builder to build the project). When restart is triggered (on master node, which is linux box) while this build is executing on windows slave, first this batch script is terminated (I guess with some kind of interrupt signal) which causes MSVC to report build as failed (MSVC reports cancelled builds as failures) and after restart this batch script is resumed, but instead of either new build with MSBuild or new call to entire batch script (which should build the project correctly) or continuing with next batch script which is followed after the one which performs the build (which actually collects test results and stashes them so later master node can utilize XUnit publisher plugin to publish test results), the job simply hangs and does nothing indefinitely (until someone logs in and kills it, because stop command is also ignored).
Add Comment
[JIRA] (JENKINS-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick commented on JENKINS-33761 Re: Ability to disable "resume" build. jobs that were restarted during perfoming network operations inside shell script which were frozen after resume and could not be stopped in any way If this is reproducible somehow I would consider it a high-priority bug to be fixed. Ditto for the other scenarios, unless they are limited to usage of some particular plugin. simply add this simple checkbox Adding a checkbox is of course simple. Making it do what you request is not necessarily simple and would require significant study. CpsThreadGroup.saveProgram can easily be suppressed (possibly the CPS transform could even be disabled), and WorkflowRun.onLoad could easily be made to fail a build which had not terminated cleanly, and CpsFlowExecution.blocksRestart could be made to unconditionally return true. But then you will still get unreleased workspace locks and the like. Possibly there is some way a Terminator could throw ThreadDeath into the Groovy call stack to try to unwind blocks cleanly. 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
[JIRA] (JENKINS-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33761 Ability to disable "resume" build. Change By: Jesse Glick Issue Type: Improvement New Feature 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-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33761 Ability to disable "resume" build. Change By: Jesse Glick Component/s: workflow-cps-plugin 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-33761) Ability to disable "resume" build.
Title: Message Title Nenad Miksa edited a comment on JENKINS-33761 Re: Ability to disable "resume" build. [~jglick], I am aware that resuming build is one of the core features of pipeline and that you would very much like it to work by default, however from my experience most of the plugins do not properly support resuming the build (i.e. they have bugs, not that they do not deliberately support it). After restarting the Jenkins (mostly due to plugin updates), I've seen jobs resuming without taking any executors, jobs taking an executor and just waiting something to happen (which never happens , i.e. waiting is infinite ), jobs which do the same thing (that was already done) after being resumed, plugins failing to parse XML test reports after being "resumed" in the middle of the process, jobs that were restarted during perfoming network operations inside shell script which were frozen after resume and could not be stopped in any way (neither with stop nor with kill - we had to manually remove the job from database while jenkins was offline to stop this job from resuming), ...Please be aware that jenkins is also used by software developers that do not develop in Java (which is natively supported by jenkins) and that we do some very weird things in our build scripts to support behaviour and flexibility we need (for example, in my case I need to clone repository on SSD, while one of its submodules must be cloned on rotational disk - such a use case will never be supported by default jenkins scm plugins and I must therefore write my on build script which does that, and improper/buggy resuming of such a script usually makes the executor wait indefinitely for something which never happens, so I must manually kill the build (yes, kill, because stop is also ignored)).For such proper supporting such use cases, there are two ways - either add support in every plugin for every use case (no matter how weird it is) and make it correctly work in all cases, including bug-free resuming build on multi-node heterogenous system - which is nearly impossible, or simply add this simple checkbox saying "disable resuming of build" which will either prevent jenkins to be restarted while build is ongoing (behaviour of freestyle job), or simply fail the build. Yes, failing the build is not technically correct, but it is exactly what is currently happening for us, except after resuming, a engineer needs to log into the jenkins and manually kill the zombie build which only waits and never properly resumes. Add Comment
[JIRA] (JENKINS-33761) Ability to disable "resume" build.
Title: Message Title Nenad Miksa commented on JENKINS-33761 Re: Ability to disable "resume" build. Jesse Glick, I am aware that resuming build is one of the core features of pipeline and that you would very much like it to work by default, however from my experience most of the plugins do not properly support resuming the build (i.e. they have bugs, not that they do not deliberately support it). After restarting the Jenkins (mostly due to plugin updates), I've seen jobs resuming without taking any executors, jobs taking an executor and just waiting something to happen (which never happens), jobs which do the same thing after being resumed, plugins failing to parse XML test reports after being "resumed" in the middle of the process, jobs that were restarted during perfoming network operations inside shell script which were frozen after resume and could not be stopped in any way (neither with stop nor with kill - we had to manually remove the job from database while jenkins was offline to stop this job from resuming), ... Please be aware that jenkins is also used by software developers that do not develop in Java (which is natively supported by jenkins) and that we do some very weird things in our build scripts to support behaviour and flexibility we need (for example, in my case I need to clone repository on SSD, while one of its submodules must be cloned on rotational disk - such a use case will never be supported by default jenkins scm plugins and I must therefore write my on build script which does that, and improper/buggy resuming of such a script usually makes the executor wait indefinitely for something which never happens, so I must manually kill the build (yes, kill, because stop is also ignored)). For such proper supporting such use cases, there are two ways - either add support in every plugin for every use case (no matter how weird it is) and make it correctly work in all cases, including bug-free resuming build on multi-node heterogenous system - which is nearly impossible, or simply add this simple checkbox saying "disable resuming of build" which will either prevent jenkins to be restarted while build is ongoing (behaviour of freestyle job), or simply fail the build. Yes, failing the build is not technically correct, but it is exactly what is currently happening for us, except after resuming, a engineer needs to log into the jenkins and manually kill the zombie build which only waits and never properly resumes. Add Comment
[JIRA] (JENKINS-33761) Ability to disable "resume" build.
Title: Message Title Charlie Groves commented on JENKINS-33761 Re: Ability to disable "resume" build. Not really. While the build is running normally, we don't want anyone to have to confirm proceeding to the next step. It's only when the build is interrupted by a restart that we don't want it to automatically continue. Whenever Jenkins goes down, it's generally a larger failure with a variable amount of time before service is restored. We can't guarantee that the person watching it will be there when Jenkins comes back without making the normal case worse. 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-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick commented on JENKINS-33761 Re: Ability to disable "resume" build. I think what you are looking for is an input step between stages. Whether Jenkins happened to be restarted in the middle of the build is not relevant to that. 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-33761) Ability to disable "resume" build.
Title: Message Title Charlie Groves commented on JENKINS-33761 Re: Ability to disable "resume" build. Ahh, well what we want is for it not to continue without someone being there to monitor it. Automatically continuing to the next step means that if the person previously monitoring it left after Jenkins went down, they wouldn't be there when it comes back. We'd like to not have it resume for those builds. 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-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick commented on JENKINS-33761 Re: Ability to disable "resume" build. maybe the problem is with finding the process again, or handling it not being there Perhaps. Should it handle bat() and sh()? Yes, this is the principle use case. Is the assumption that the slave keeps track of the process output, return value etc.? Yes. Will a job always resume to the same slave? Yes. Maybe the build finished before Jenkins came back? The external process I suppose you mean. Should be fine, the sh/bat step should then simply print any final output, and exit according to the process’ exit code. it'd continue to the next step after that? Exactly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33761) Ability to disable "resume" build.
Title: Message Title Charlie Groves commented on JENKINS-33761 Re: Ability to disable "resume" build. If true, that is a bug in the EC2 plugin. It is supposed to keep the agent connected for the entire duration of the build. Maybe the build finished before Jenkins came back? It doesn't really change that we'd prefer not to resume these builds. Pipeline does not restart any build steps when Jenkins is restarted. It simply lets the existing process continue running and displaying output (or it might have ended on its own during the Jenkins restart). Oh, it was my understanding that it'd continue to the next step after that? Does it only complete the current step and stop? 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-33761) Ability to disable "resume" build.
Title: Message Title Russell Gallop edited a comment on JENKINS-33761 Re: Ability to disable "resume" build. I'd be happy with resume either working or there being an option to disable it.> I've also never ever seen it work correctly...Likewise but maybe it happens without my noticing :-)> Pipeline does not restart any build steps when Jenkins is restarted. It simply lets the existing process continue running and displaying output (or it might have ended on its own during the Jenkins restart).In the cases where we see resume hanging there is no process running so maybe the problem is with finding the process again, or handling it not being there.Should it handle bat() and sh()? Is the assumption that the slave keeps track of the process output, return value etc.? Will a job always resume to the same slave? 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-33761) Ability to disable "resume" build.
Title: Message Title Russell Gallop commented on JENKINS-33761 Re: Ability to disable "resume" build. I'd be happy with resume either working or there being an option to disable it. > I've also never ever seen it work correctly... Likewise but maybe it happens without my noticing > Pipeline does not restart any build steps when Jenkins is restarted. It simply lets the existing process continue running and displaying output (or it might have ended on its own during the Jenkins restart). In the cases where we see resume hanging there is no process running so maybe the problem is with finding the process again, or handling it not being there. Should it handle bat() and sh()? Is the assumption that the slave keeps track of the process output, return value etc.? 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-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick commented on JENKINS-33761 Re: Ability to disable "resume" build. We run builds on ephemeral EC2 agents. If Jenkins is restarted, the agents are often dead by the time Jenkins is back. If true, that is a bug in the EC2 plugin. It is supposed to keep the agent connected for the entire duration of the build. they not be restarted automatically Pipeline does not restart any build steps when Jenkins is restarted. It simply lets the existing process continue running and displaying output (or it might have ended on its own during the Jenkins restart). 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-33761) Ability to disable "resume" build.
Title: Message Title Charlie Groves commented on JENKINS-33761 Re: Ability to disable "resume" build. There are a couple cases: We run builds on ephemeral EC2 agents. If Jenkins is restarted, the agents are often dead by the time Jenkins is back. Those builds just hang looking for the agent. We run deploys that require someone to monitor them. We'd prefer that they not be restarted automatically, that instead someone be there to start and watch them. 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-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick commented on JENKINS-33761 Re: Ability to disable "resume" build. a few builds where it doesn't make sense to resume them Because they intrinsically could not be resumed? Or you just do not really care about loss of a build or two? 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-33761) Ability to disable "resume" build.
Title: Message Title Charlie Groves commented on JENKINS-33761 Re: Ability to disable "resume" build. I would also really appreciate the ability to disable resumption. We have a few builds where it doesn't make sense to resume them, so it'd be better to have it off completely. 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-33761) Ability to disable "resume" build.
Title: Message Title
davidkarlsen edited a comment on JENKINS-33761
Re: Ability to disable "resume" build.
Got same problem.{noformat}Resuming build at Fri Sep 30 16:18:26 CEST 2016 after Jenkins restartReady to run at Fri Sep 30 16:18:28 CEST 2016{noformat}and then it just sits there. threaddump:{noformat}Thread #6 at DSL.emailext(not yet scheduled) at standardBuild.call(/data/jenkins/workflow-libs/vars/standardBuild.groovy:101) at DSL.sshagent(Native Method) at standardBuild.call(/data/jenkins/workflow-libs/vars/standardBuild.groovy:28) at DSL.ws(Native Method) at standardBuild.call(/data/jenkins/workflow-libs/vars/standardBuild.groovy:27) at DSL.node(running on slave24-rhel) at standardBuild.call(/data/jenkins/workflow-libs/vars/standardBuild.groovy:25) at WorkflowScript.run(WorkflowScript:15){noformat}seems to be stuck in emailext
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-33761) Ability to disable "resume" build.
Title: Message Title
davidkarlsen edited a comment on JENKINS-33761
Re: Ability to disable "resume" build.
Got same problem.{noformat}Resuming build at Fri Sep 30 16:18:26 CEST 2016 after Jenkins restartReady to run at Fri Sep 30 16:18:28 CEST 2016{noformat}and then it just sits there.
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-33761) Ability to disable "resume" build.
Title: Message Title
davidkarlsen edited a comment on JENKINS-33761
Re: Ability to disable "resume" build.
Got same problem. {noformat}Resuming build at Fri Sep 30 16:18:26 CEST 2016 after Jenkins restartReady to run at Fri Sep 30 16:18:28 CEST 2016{noformat}and then it just sits there.
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-33761) Ability to disable "resume" build.
Title: Message Title davidkarlsen commented on JENKINS-33761 Re: Ability to disable "resume" build. Got same problem. 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-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick commented on JENKINS-33761 Re: Ability to disable "resume" build. Resuming build after restart starts the scripts from the beginning Never heard of such a bug and cannot even imagine how it could occur. If you have steps to reproduce from scratch, please file separately. 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-33761) Ability to disable "resume" build.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33761 Ability to disable "resume" build. Change By: Jesse Glick Component/s: workflow-job-plugin Component/s: pipeline 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.
