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

With 'HP Application Automation Tools' v5.1 installed running a pipeline from script stored in Perforce results in NPE

XMLWordPrintable

      Trying to run a pipeline job with the pipeline groovy script downloaded from Perforce (with the P4 plugin) fails with a null pointer exception (NPE).

      java.lang.NullPointerException
	at com.hp.application.automation.tools.octane.events.SCMListenerImpl.onChangeLogParsed(SCMListenerImpl.java:84)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:751)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1500(WorkflowRun.java:125)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:936)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:123)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:130)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:59)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:232)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:404)

      Note that the exact same configuration works without any issues when using HP Application Automation Tools v5.0 instead of v5.1.

          [JENKINS-42580] With 'HP Application Automation Tools' v5.1 installed running a pipeline from script stored in Perforce results in NPE

          Yafim Kazak added a comment -

          Could you please add here or send to Kazak[at]hpe[dot]com the following -

          <jenkins installation on master>\jobs\<job name>\config.xml

          zip whole folder - <jenkins installation on master>\jobs\<job name>\builds\<bad build number>

           

          Thanks ahaed.

           

          Yafim Kazak added a comment - Could you please add here or send to Kazak [at] hpe [dot] com the following - <jenkins installation on master>\jobs\<job name>\config.xml zip whole folder - <jenkins installation on master>\jobs\<job name>\builds\<bad build number>   Thanks ahaed.  

          Frédéric Meyrou added a comment -

          Files sent today by eMail.

          KR,

           

          ./FM

          Frédéric Meyrou added a comment - Files sent today by eMail. KR,   ./FM

          Robby Pocase added a comment -

          I'm getting this error on my Perforce instance as well. Seems to be occurring on both classic depots and streams.

          Robby Pocase added a comment - I'm getting this error on my Perforce instance as well. Seems to be occurring on both classic depots and streams.

          Robby Pocase added a comment -

          For my specific use case, I'm able to work around this using try/catch.

           

          try {
  p4sync args
} catch (NullPointerException e) {
  echo "Ignoring NPE"
}

          Robby Pocase added a comment - For my specific use case, I'm able to work around this using try/catch.   try { p4sync args } catch (NullPointerException e) { echo "Ignoring NPE" }

          Yafim Kazak added a comment - - edited

          This should be resolved in our latest beta release 5.1.0.2 and will be formally released in Aug 2017

          • To get the beta follow the instruction here:

          https://hpsa.github.io/JenkinsPluginUpdateCenter/

          • Or download it manually:

          https://updates.jenkins-ci.org/experimental/latest/hp-application-automation-tools-plugin.hpi

          Yafim Kazak added a comment - - edited This should be resolved in our latest beta release 5.1.0.2 and will be formally released in Aug 2017 To get the beta follow the instruction here: https://hpsa.github.io/JenkinsPluginUpdateCenter/ Or download it manually: https://updates.jenkins-ci.org/experimental/latest/hp-application-automation-tools-plugin.hpi

          Raphael Pionke added a comment -

          yafim_kazak this issue breaks nearly every build on our productive CI system. We can't use the plugin anymore. Why dont you fix this asap as version 5.1.1 or something like this? 

          Raphael Pionke added a comment - yafim_kazak this issue breaks nearly every build on our productive CI system. We can't use the plugin anymore. Why dont you fix this asap as version 5.1.1 or something like this? 

          Yafim Kazak added a comment -

          Hi - it was resolved in 5.1.0.2.

          Please download it and update us if it still continuous.

          Yafim Kazak added a comment - Hi - it was resolved in 5.1.0.2. Please download it and update us if it still continuous.

          Jeroen Bogers added a comment -

          rpionke, if you are unwilling to run a beta version you can always revert back to 5.0 as that version still works. We are running 5.0 on our systems for this reason. We will probably wait until 5.1.0.2 is officially released before we upgrade again.

          Jeroen Bogers added a comment - rpionke , if you are unwilling to run a beta version you can always revert back to 5.0 as that version still works. We are running 5.0 on our systems for this reason. We will probably wait until 5.1.0.2 is officially released before we upgrade again.

          Sezen de Bruijn added a comment -

          Came across the exact same issue within version 5.2. Could it have been reintroduced?

          Sezen de Bruijn added a comment - Came across the exact same issue within version 5.2. Could it have been reintroduced?

          Roy Lu added a comment -

          Hi yafim_kazak,

          I saw you reopened this. Is it still not resolved?

          Roy Lu added a comment - Hi yafim_kazak , I saw you reopened this. Is it still not resolved?

            mseldin Michael Seldin
            jbogers Jeroen Bogers
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: