We perform many concurrent builds in one job and are using the email-ext plugin. Sometimes and older build takes longer time to finish and then the new jobs just waits to be finished because BuildStepMonitor.BUILD is configured in the plugin.

      Could this one line be changed?

          [JENKINS-26032] Prefer BuildStepMonitor.NONE

          Sandeep Dhingra added a comment - - edited

          Please fix this for performance publisher plugin.We face same issue there as with email ext

          https://github.com/jenkinsci/performance-plugin/search?utf8=%E2%9C%93&q=BuildStepMonitor+getRequiredMonitorService

          Sandeep Dhingra added a comment - - edited Please fix this for performance publisher plugin.We face same issue there as with email ext https://github.com/jenkinsci/performance-plugin/search?utf8=%E2%9C%93&q=BuildStepMonitor+getRequiredMonitorService

          Sorry for above comment,that may not solve the problem
          I think ,I wish to have same behavior as https://issues.jenkins-ci.org/browse/JENKINS-9913 with this plugin
          "Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent".Concurrent tasks should NOT be blocked for unnecessary checkpoint

          Sandeep Dhingra added a comment - Sorry for above comment,that may not solve the problem I think ,I wish to have same behavior as https://issues.jenkins-ci.org/browse/JENKINS-9913 with this plugin "Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent".Concurrent tasks should NOT be blocked for unnecessary checkpoint

          Sandeep Dhingra added a comment - - edited

          Jesse the component is performance plugin

          Sandeep Dhingra added a comment - - edited Jesse the component is performance plugin

          Actually we need similar fixes as done for this
          https://github.com/jglick/email-ext-plugin/commit/6fb41818d63ca0067171f8c01fcdbed196335b44

          Thanks
          Sandeep

          Sandeep Dhingra added a comment - Actually we need similar fixes as done for this https://github.com/jglick/email-ext-plugin/commit/6fb41818d63ca0067171f8c01fcdbed196335b44 Thanks Sandeep

          Daniel Beck added a comment -

          File one issue per plugin. They generally have different authors.

          Daniel Beck added a comment - File one issue per plugin. They generally have different authors.

          Sandeep Dhingra added a comment - - edited

          Hi Daniel ,
          The issue is performance summariser doesn't work if we change BuildStepMonitor.BUILD to Build.NONE.We want the report to get published after the test is over.Though we see *.jtl files,the report doesn't get published.
          Thanks
          Sandeep

          Sandeep Dhingra added a comment - - edited Hi Daniel , The issue is performance summariser doesn't work if we change BuildStepMonitor.BUILD to Build.NONE.We want the report to get published after the test is over.Though we see *.jtl files,the report doesn't get published. Thanks Sandeep

          Closing this as I already opened new one and sponsored that too.The issue and acceptance criteria are listed in detail
          https://issues.jenkins-ci.org/browse/JENKINS-26515

          Sandeep Dhingra added a comment - Closing this as I already opened new one and sponsored that too.The issue and acceptance criteria are listed in detail https://issues.jenkins-ci.org/browse/JENKINS-26515

          https://issues.jenkins-ci.org/browse/JENKINS-26515 is more complete and issue which should be tracked and fixed and has money associated

          Sandeep Dhingra added a comment - https://issues.jenkins-ci.org/browse/JENKINS-26515 is more complete and issue which should be tracked and fixed and has money associated

            manolo Manuel Carrasco
            forsandeep Sandeep Dhingra
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: