Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-27323

Out of index error with logLines defaulting to 0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • notification-plugin
    • None
    • Jenkins 1.602
      Plugin Version 1.9

      With the logLines config option, the default value is 0.
      This causes an out of bounds issue. I had to manually change the value to -1 to address this.

      java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
      at java.util.LinkedList.checkElementIndex(LinkedList.java:553)
      at java.util.LinkedList.set(LinkedList.java:488)
      at hudson.model.Run.getLog(Run.java:1962)
      at com.tikal.hudson.plugins.notification.Phase.getLog(Phase.java:141)
      at com.tikal.hudson.plugins.notification.Phase.buildJobState(Phase.java:79)
      at com.tikal.hudson.plugins.notification.Phase.handle(Phase.java:42)
      at com.tikal.hudson.plugins.notification.JobListener.onStarted(JobListener.java:31)
      at hudson.model.listeners.RunListener.fireStarted(RunListener.java:213)
      at hudson.model.Run.execute(Run.java:1746)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:89)
      at hudson.model.Executor.run(Executor.java:240)

          [JENKINS-27323] Out of index error with logLines defaulting to 0

          Kevin R. created issue -
          John Vines made changes -
          Link New: This issue is related to JENKINS-27441 [ JENKINS-27441 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 161528 ] New: JNJira + In-Review [ 180732 ]
          Alexander A made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Alexander A made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Unassigned Unassigned
            chr0n1x Kevin R.
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: