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

NPE when labeling build

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      Windows2003, Tomcat 6.0.20, Java 1.6.0_06
    • Similar Issues:

      Description

      I'm using 1.375 with the latest version of the Perforce plugin. From the logs, I'm not sure what might be misconfigured, but I'm getting it consistently. Just hoping the error might provide clues as to the problem.

      At the end of the build, the label (disk) icon appears next to the build list with the correct value, the build fails on this error. I've tried other simpler labels ${JOB_NAME}, etc. besides the one shown.

      Labelling Build in Perforce using ${JOB_NAME}-b${BUILD_NUMBER}
      ERROR: Publisher hudson.plugins.perforce.PerforceTagNotifier aborted due to exception
      java.lang.NullPointerException
      at hudson.plugins.perforce.PerforceSCM.parseProjectPath(PerforceSCM.java:1340)
      at hudson.plugins.perforce.PerforceTagAction.tagBuild(PerforceTagAction.java:146)
      at hudson.plugins.perforce.PerforceTagNotifier.perform(PerforceTagNotifier.java:76)
      at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
      at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601)
      at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580)
      at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:558)
      at hudson.model.Build$RunnerImpl.post2(Build.java:158)
      at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
      at hudson.model.Run.run(Run.java:1296)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:129)

        Attachments

          Activity

          Hide
          rpetti Rob Petti added a comment -

          Thanks for the bug report. There's a bunch of stuff that isn't playing nice with the new client workspace name substitution feature, and I suspect this may be one of them.

          Show
          rpetti Rob Petti added a comment - Thanks for the bug report. There's a bunch of stuff that isn't playing nice with the new client workspace name substitution feature, and I suspect this may be one of them.
          Hide
          rpetti Rob Petti added a comment -

          Out of curiosity, are you letting hudson manage your client workspace?

          Show
          rpetti Rob Petti added a comment - Out of curiosity, are you letting hudson manage your client workspace?
          Hide
          jed624 jed624 added a comment -

          Thanks for looking into this quickly. No - we manage our workspaces. I can't really even try that option - if hudson managed them, it could cause problems.

          Show
          jed624 jed624 added a comment - Thanks for looking into this quickly. No - we manage our workspaces. I can't really even try that option - if hudson managed them, it could cause problems.
          Hide
          rpetti Rob Petti added a comment -

          That would be why then... Support for that has sort of fallen by the wayside, since it's far easier to let hudson take care of it. I'll work on a solution.

          What sort of problems would you foresee by letting hudson manage it for you?

          Show
          rpetti Rob Petti added a comment - That would be why then... Support for that has sort of fallen by the wayside, since it's far easier to let hudson take care of it. I'll work on a solution. What sort of problems would you foresee by letting hudson manage it for you?
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : rpetti
          Path:
          trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java
          http://jenkins-ci.org/commit/35243
          Log:
          [FIXED JENKINS-7558] fixing labelling when client not being managed by hudson. Additionally, the Views field in the plugin config will be populated with the contents of the view from perforce.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : rpetti Path: trunk/hudson/plugins/perforce/src/main/java/hudson/plugins/perforce/PerforceSCM.java http://jenkins-ci.org/commit/35243 Log: [FIXED JENKINS-7558] fixing labelling when client not being managed by hudson. Additionally, the Views field in the plugin config will be populated with the contents of the view from perforce.
          Hide
          jed624 jed624 added a comment -

          Thanks for fixing the bug. Our situation is probably unique. We have workspace views built programmatically using p4 commands from the state of build solutions and projects we need to have for that build. We can manage this well through perforce, but so far not yet tried to populate the view in hudson. Of course, we could label the build ourselves too, but when I noticed the option I had to try it out.

          Show
          jed624 jed624 added a comment - Thanks for fixing the bug. Our situation is probably unique. We have workspace views built programmatically using p4 commands from the state of build solutions and projects we need to have for that build. We can manage this well through perforce, but so far not yet tried to populate the view in hudson. Of course, we could label the build ourselves too, but when I noticed the option I had to try it out.

            People

            • Assignee:
              rpetti Rob Petti
              Reporter:
              jed624 jed624
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: