XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins LTS 2.60.3
      Periodic Reincarnation Plugin updated to 1.11 on 23rd of August 2017
      a lot of other plugins
    • Similar Issues:

      Description

      After upgrading our instance yesterday some builds of jobs got stuck after they obviously finished with all build steps.

      Last console output of builds have been:
      Finished Calculation of disk usage of workspace in 0 seconds
      which stems from the Disk-Usage Plugin.

      Watching the corresponding threads with the Monitoring plugin I could see this similar stacktrace at all build threads:

      Executor #13 for NODENAME : executing JOB_NAME #BUILDNUMBER
      java.util.Collections$UnmodifiableCollection$1.hasNext(Collections.java:1041)
      java.util.Collections$UnmodifiableCollection$1.hasNext(Collections.java:1041)
      hudson.model.Run.getCause(Run.java:582)
      org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.checkRestartDepth(AfterbuildReincarnation.java:185)
      org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.noChangeRestart(AfterbuildReincarnation.java:107)
      org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:70)
      org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:18)
      hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211)
      hudson.model.Run.execute(Run.java:1780)
      hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      hudson.model.ResourceController.execute(ResourceController.java:97)
      hudson.model.Executor.run(Executor.java:405)
      

      Find attached the global configuration of the periodic reincarnation plugin in our instance. The jobs do not have a local configuration.

      I killed the corresponding build threads, then downgraded to version 1.10 of the plugin.

        Attachments

          Activity

          Hide
          jochenafuerbacher Jochen A. Fürbacher added a comment -

          We noticed such an issue if the log file of a build is too long and you use regular expressions. But this also happend in version < 1.11.

          Therefore we provided the option to use build failures from Build Failure Analyzer instead of regular expressions (if you have BFA installed). When Periodic Reincarnation performs an check on the builds, it does't check the log files on matching regular expressions anymore. It only checks, if the build has a failure cause, BFA checked on before. This reduces the duration of periodic checks a lot.

          I don't know if this solves your issue but I think it's worth to look at.

          Show
          jochenafuerbacher Jochen A. Fürbacher added a comment - We noticed such an issue if the log file of a build is too long and you use regular expressions. But this also happend in version < 1.11. Therefore we provided the option to use build failures from Build Failure Analyzer instead of regular expressions (if you have BFA installed). When Periodic Reincarnation performs an check on the builds, it does't check the log files on matching regular expressions anymore. It only checks, if the build has a failure cause, BFA checked on before. This reduces the duration of periodic checks a lot. I don't know if this solves your issue but I think it's worth to look at.
          Hide
          jochenafuerbacher Jochen A. Fürbacher added a comment -

          Please retest with Periodic Reincarnation 1.12 and give us feedback. Thank you.

          Show
          jochenafuerbacher Jochen A. Fürbacher added a comment - Please retest with Periodic Reincarnation 1.12 and give us feedback. Thank you.
          Hide
          krulls Stephan Krull added a comment -

          BTW: If you aim to work with GitHub as an issue tracker (and the new plugin homepage suggests that) you should play fair:

          • initiate archiving of the component periodic-reincarnation-plugin in this JIRA project, or
          • close each new issue for this component by linking to GitHub issue tracker or (even better)
          • automatically create GitHub issues from JIRA issues (unfortunately I don't know any ready-made solution for this)
          Show
          krulls Stephan Krull added a comment - BTW: If you aim to work with GitHub as an issue tracker (and the new plugin homepage suggests that) you should play fair: initiate archiving of the component periodic-reincarnation-plugin in this JIRA project, or close each new issue for this component by linking to GitHub issue tracker or (even better) automatically create GitHub issues from JIRA issues (unfortunately I don't know any ready-made solution for this)
          Hide
          jochenafuerbacher Jochen A. Fürbacher added a comment -

          We prefer to use JIRA as issue tracker. The issue in Github seems to be similar to this one but it isn't proven to be really the same issue, yet. So I didn't link the Github issue here.

          Anyway, JIRA is our first choice to track issues.

          Show
          jochenafuerbacher Jochen A. Fürbacher added a comment - We prefer to use JIRA as issue tracker. The issue in Github seems to be similar to this one but it isn't proven to be really the same issue, yet. So I didn't link the Github issue here. Anyway, JIRA is our first choice to track issues.
          Hide
          krulls Stephan Krull added a comment -

          Installed version 1.12.1 today. No problems with the first job runs.

          Show
          krulls Stephan Krull added a comment - Installed version 1.12.1 today. No problems with the first job runs.
          Hide
          krulls Stephan Krull added a comment -

          Just want to give you notice that I have a hung build again today with version 1.12.1 (on Jenkins 2.121.3 (LTS)). This is stacktrace of the thread:

          Executor #0 for Atlantis01 : executing T3-widgets-svogt #75
          java.util.regex.Pattern$CharProperty.match(Pattern.java:3776)
          java.util.regex.Pattern$Curly.match0(Pattern.java:4260)
          java.util.regex.Pattern$Curly.match(Pattern.java:4234)
          java.util.regex.Pattern$Start.match(Pattern.java:3461)
          java.util.regex.Matcher.search(Matcher.java:1248)
          java.util.regex.Matcher.find(Matcher.java:637)
          org.jenkinsci.plugins.periodicreincarnation.Utils.checkFile(Utils.java:304)
          org.jenkinsci.plugins.periodicreincarnation.Utils.checkBuild(Utils.java:165)
          org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.periodicTriggerRestart(AfterbuildReincarnation.java:139)
          org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:69)
          org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:18)
          hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211)
          hudson.model.Run.execute(Run.java:1843)
          hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          hudson.model.ResourceController.execute(ResourceController.java:97)
          hudson.model.Executor.run(Executor.java:429)
          

          @Jochen A. Fürbacher: This looks like it is related to this regex problem we saw before. Can you confirm?

          Show
          krulls Stephan Krull added a comment - Just want to give you notice that I have a hung build again today with version 1.12.1 (on Jenkins 2.121.3 (LTS)). This is stacktrace of the thread: Executor #0 for Atlantis01 : executing T3-widgets-svogt #75 java.util.regex.Pattern$CharProperty.match(Pattern.java:3776) java.util.regex.Pattern$Curly.match0(Pattern.java:4260) java.util.regex.Pattern$Curly.match(Pattern.java:4234) java.util.regex.Pattern$Start.match(Pattern.java:3461) java.util.regex.Matcher.search(Matcher.java:1248) java.util.regex.Matcher.find(Matcher.java:637) org.jenkinsci.plugins.periodicreincarnation.Utils.checkFile(Utils.java:304) org.jenkinsci.plugins.periodicreincarnation.Utils.checkBuild(Utils.java:165) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.periodicTriggerRestart(AfterbuildReincarnation.java:139) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:69) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:18) hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211) hudson.model.Run.execute(Run.java:1843) hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) hudson.model.ResourceController.execute(ResourceController.java:97) hudson.model.Executor.run(Executor.java:429) @ Jochen A. Fürbacher : This looks like it is related to this regex problem we saw before. Can you confirm?

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            krulls Stephan Krull
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: