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

latest version of jobConfigHistory fails on the first run when using a matrix job

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When running a matrix job for the first time (or when assigning new build slaves to the job) the job fails right away with the error bellow:

      FATAL: null
      java.lang.NullPointerException
      at hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:60)
      at hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:27)
      at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188)
      at hudson.model.Run.run(Run.java:1403)
      at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:238)
      

        Attachments

          Activity

          Hide
          celltestr celltestr added a comment -

          Downgraded to version 2.0 and I can't reproduce this issue.. Looks like this was introduced with the new badges feature..

          Show
          celltestr celltestr added a comment - Downgraded to version 2.0 and I can't reproduce this issue.. Looks like this was introduced with the new badges feature..
          Hide
          mfriedenhagen Mirko Friedenhagen added a comment -

          Kathi, what happens when this is the first execution and in https://github.com/kstutz/jobConfigHistory-plugin/blob/9626f165d5034bad20660e2bc047c641d1f13cc5/src/main/java/hudson/plugins/jobConfigHistory/JobConfigBadgeAction.java#L56 the nextBuildNumber is 1? We need to check for the length of builds as well, probably.

          Show
          mfriedenhagen Mirko Friedenhagen added a comment - Kathi, what happens when this is the first execution and in https://github.com/kstutz/jobConfigHistory-plugin/blob/9626f165d5034bad20660e2bc047c641d1f13cc5/src/main/java/hudson/plugins/jobConfigHistory/JobConfigBadgeAction.java#L56 the nextBuildNumber is 1? We need to check for the length of builds as well, probably.
          Hide
          kstutz Kathi Stutz added a comment -

          This will be fixed in the next version of the plugin, which will be released in February.

          Show
          kstutz Kathi Stutz added a comment - This will be fixed in the next version of the plugin, which will be released in February.
          Hide
          kstutz Kathi Stutz added a comment -

          Version 2.3, which includes a fix for this bug, has been released two days ago.

          Show
          kstutz Kathi Stutz added a comment - Version 2.3, which includes a fix for this bug, has been released two days ago.
          Hide
          brian Brian Murrell added a comment - - edited

          It seems like this has been re-introduced with version 2.5 since I'm seeing this again with the 2.5 plugin on my 1.498 release of Jenkins.

          Oh, but on second look, it's happening for non-matrix jobs in my case.

          Show
          brian Brian Murrell added a comment - - edited It seems like this has been re-introduced with version 2.5 since I'm seeing this again with the 2.5 plugin on my 1.498 release of Jenkins. Oh, but on second look, it's happening for non-matrix jobs in my case.
          Hide
          jochenafuerbacher Jochen A. Fürbacher added a comment -

          Can't reproduce with JCH 2.15 and core 2.52.

          Brian Murrell: Does your problem still occur? If so, what kind ob jobs fail?

          Show
          jochenafuerbacher Jochen A. Fürbacher added a comment - Can't reproduce with JCH 2.15 and core 2.52. Brian Murrell : Does your problem still occur? If so, what kind ob jobs fail?
          Hide
          brianjmurrell Brian J Murrell added a comment -

          Jochen A. Fürbacher: I'm afraid with my comment on this issue being over 3 years old now, I have no recollection.

          Show
          brianjmurrell Brian J Murrell added a comment - Jochen A. Fürbacher : I'm afraid with my comment on this issue being over 3 years old now, I have no recollection.

            People

            • Assignee:
              Unassigned
              Reporter:
              celltestr celltestr
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: