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

[RTC Plugin] NullPointerException

    Details

    • Similar Issues:

      Description

      $ scm accept -u ******** -P ******** -d D:\Jenkins\jobs\RTC-Artemis-Main-HSQL\workspace -s "Main Artemis Dev" --flow-components -o -v -c 8244 8246

      Espace de travail inchangé.

      FATAL: null
      java.lang.NullPointerException
      at com.deluan.jenkins.plugins.rtc.changelog.JazzChangeSet.copyItemsFrom(JazzChangeSet.java:150)
      at com.deluan.jenkins.plugins.rtc.JazzClient.accept(JazzClient.java:112)
      at com.deluan.jenkins.plugins.rtc.JazzSCM.checkout(JazzSCM.java:104)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1324)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
      at hudson.model.Run.execute(Run.java:1518)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:236)

        Attachments

          Activity

          Hide
          dbeerens Danny Beerens added a comment - - edited

          I previously added my complaint to the comments failing to realize to check the Issue Log of this plugin. Hence this remark here:

          From the logs of Jenkins, it appears as if the 'lscm accept'-function is called without the login details (i.e. -r & -u & -P parameters). Because the function doesn't know which RTC Repository to contact, it throws the java.NullPointerException's.

          By-the-way: All previously called lscm commands are called with these login details. And if you run the lscm accept command yourself from the command line, using the login details, all is okay.

          We now have a command script running as a work-around, but we'd REALLY like this issue solved.

          Show
          dbeerens Danny Beerens added a comment - - edited I previously added my complaint to the comments failing to realize to check the Issue Log of this plugin. Hence this remark here: From the logs of Jenkins, it appears as if the 'lscm accept'-function is called without the login details (i.e. -r & -u & -P parameters). Because the function doesn't know which RTC Repository to contact, it throws the java.NullPointerException's. By-the-way: All previously called lscm commands are called with these login details. And if you run the lscm accept command yourself from the command line, using the login details, all is okay. We now have a command script running as a work-around, but we'd REALLY like this issue solved.

            People

            • Assignee:
              deluan Deluan Quint√£o
              Reporter:
              bokc bokc
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: