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

NPE exception for new perforce plugin when used in Multi SCM

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • p4-plugin
    • jenkins 1.630 p4 plugin 1.3.1

      Getting NPE exception at the end of the build when new perforce plugin is used in multi scm section.

      Below is exception trace
      FATAL: null
      java.lang.NullPointerException
      at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:676)
      at hudson.model.Run.execute(Run.java:1766)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:98)
      at hudson.model.Executor.run(Executor.java:408)

      Note that there is no issue if used independently.

          [JENKINS-32064] NPE exception for new perforce plugin when used in Multi SCM

          suresh nallamilli created issue -
          suresh nallamilli made changes -
          Summary Original: NPE exception when used in Multi SCM New: NPE exception for new perforce plugin when used in Multi SCM
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 167540 ] New: JNJira + In-Review [ 182777 ]
          Paul Allen made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Paul Allen added a comment -

          Paul Allen added a comment - Fix ready for release: https://swarm.workshop.perforce.com/reviews/20167/
          Paul Allen made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          Paul Allen added a comment -

          Released in 1.4.7

          Paul Allen added a comment - Released in 1.4.7
          Paul Allen made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Unassigned Unassigned
            snallami suresh nallamilli
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: