• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: emotional-jenkins-plugin
• Labels:

  None
• Environment:

  2.19.1

[JENKINS-44003] Emotional Jenkins plugin gets stuck for a long time in concurrent builds

Aditya Joshi created issue - 2017-05-03 04:38

Aditya Joshi made changes - 2017-05-03 04:43

Description

Original: With the Emotional Jenkins enabled in the post build step, when the job is allowed to run concurrently, builds frequently get stuck at "Emotional Jenkins is waiting for a checkpoint on ...<reference to a previous build that is still running>"   The issue is likely related to https://issues.jenkins-ci.org/browse/JENKINS-9913&#xA0;and similar issues have been fixed https://issues.jenkins-ci.org/browse/JENKINS-10234 This line in [EmotionalJenkinsPublisher.java|https://github.com/masanobuimai/emotional-jenkins-plugin/blob/master/src/main/java/org/jenkinsci/plugins/emotional_jenkins/EmotionalJenkinsPublisher.java] may need to be changed.   {code:java}  public BuildStepMonitor getRequiredMonitorService() {         return BuildStepMonitor.BUILD;   } {code}

New: With the Emotional Jenkins enabled in the post build step, when the job is allowed to run concurrently, builds frequently get stuck at "Emotional Jenkins is waiting for a checkpoint on ...<reference to a previous build that is still running>" For example, if my job's name is "myJob" and I run build #314 and #315 concurrently. If #315 completes all the build steps before #314, the build #315 would have this message in the console log: *Emotional Jenkins is waiting for a checkpoint on myJob - 314* The issue is likely related to https://issues.jenkins-ci.org/browse/JENKINS-9913&#xA0;and similar issues have been fixed https://issues.jenkins-ci.org/browse/JENKINS-10234 This line in [EmotionalJenkinsPublisher.java|https://github.com/masanobuimai/emotional-jenkins-plugin/blob/master/src/main/java/org/jenkinsci/plugins/emotional_jenkins/EmotionalJenkinsPublisher.java] may need to be changed.   {code:java}  public BuildStepMonitor getRequiredMonitorService() {         return BuildStepMonitor.BUILD;   } {code}

Aditya Joshi made changes - 2017-05-03 04:44

Description

Original: With the Emotional Jenkins enabled in the post build step, when the job is allowed to run concurrently, builds frequently get stuck at "Emotional Jenkins is waiting for a checkpoint on ...<reference to a previous build that is still running>" For example, if my job's name is "myJob" and I run build #314 and #315 concurrently. If #315 completes all the build steps before #314, the build #315 would have this message in the console log: *Emotional Jenkins is waiting for a checkpoint on myJob - 314* The issue is likely related to https://issues.jenkins-ci.org/browse/JENKINS-9913&#xA0;and similar issues have been fixed https://issues.jenkins-ci.org/browse/JENKINS-10234 This line in [EmotionalJenkinsPublisher.java|https://github.com/masanobuimai/emotional-jenkins-plugin/blob/master/src/main/java/org/jenkinsci/plugins/emotional_jenkins/EmotionalJenkinsPublisher.java] may need to be changed.   {code:java}  public BuildStepMonitor getRequiredMonitorService() {         return BuildStepMonitor.BUILD;   } {code}

New: With the Emotional Jenkins enabled in the post build step, when the job is allowed to run concurrently, builds frequently get stuck at "Emotional Jenkins is waiting for a checkpoint on ...<reference to a previous build that is still running>" For example, if my job's name is "myJob" and I run build #314 and #315 concurrently. If #315 completes all the build steps before #314, the build #315 would have this message in the console log: {quote}Emotional Jenkins is waiting for a checkpoint on myJob - 314 {quote}   The issue is likely related to https://issues.jenkins-ci.org/browse/JENKINS-9913&#xA0;and similar issues have been fixed https://issues.jenkins-ci.org/browse/JENKINS-10234 This line in [EmotionalJenkinsPublisher.java|https://github.com/masanobuimai/emotional-jenkins-plugin/blob/master/src/main/java/org/jenkinsci/plugins/emotional_jenkins/EmotionalJenkinsPublisher.java] may need to be changed.   {code:java}  public BuildStepMonitor getRequiredMonitorService() {         return BuildStepMonitor.BUILD;   } {code}