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

IvyTrigger reports [ERROR] - Polling error...

    Details

    • Similar Issues:

      Description

      Using Jenkins 1.526 and ivyTrigger 0.30 polling always fails.
      Checking the logs I see nothing.

      Interestingly when enabling debug on the ivyTrigger for that job and disabling it afterwards (while allowing the job to build in-between) seems to solve the issue only on that particular job. When Jenkins is restarted the problem is back.

      Exact output:

      [IvyTrigger] - Poll with an Ivy script

      Polling started on Sep 3, 2013 6:33:48 PM
      Polling for the job XXXXXXXX
      Looking nodes where the poll can be run.
      Looking for the last built on node.

      Polling on master.
      [ERROR] - Polling error...

        Attachments

          Activity

          Hide
          alex_ouzounis Alex Ouzounis added a comment -

          Checking /var/logs/jenkins/jenkins.log I see hundreds possibly thousands (we have many jobs that depend on the ivytrigger) of the following:

          java.lang.NullPointerException
          at org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.checkIfModified(AbstractTriggerByFullContext.java:53)
          at org.jenkinsci.lib.xtrigger.AbstractTrigger$Runner.run(AbstractTrigger.java:199)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
          at java.lang.Thread.run(Thread.java:722)

          Show
          alex_ouzounis Alex Ouzounis added a comment - Checking /var/logs/jenkins/jenkins.log I see hundreds possibly thousands (we have many jobs that depend on the ivytrigger) of the following: java.lang.NullPointerException at org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.checkIfModified(AbstractTriggerByFullContext.java:53) at org.jenkinsci.lib.xtrigger.AbstractTrigger$Runner.run(AbstractTrigger.java:199) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722)
          Hide
          alex_ouzounis Alex Ouzounis added a comment -

          Looking at the xtrigger-lib source code I see a commit highly relevant to the error I report so I assume this has been attempted to be fixed already even though I did not find any issues related.

          https://github.com/jenkinsci/xtrigger-lib/commit/f8987aa737d76107d257bc74e2ffd26456359276

          Show
          alex_ouzounis Alex Ouzounis added a comment - Looking at the xtrigger-lib source code I see a commit highly relevant to the error I report so I assume this has been attempted to be fixed already even though I did not find any issues related. https://github.com/jenkinsci/xtrigger-lib/commit/f8987aa737d76107d257bc74e2ffd26456359276
          Hide
          alex_ouzounis Alex Ouzounis added a comment -

          after uninstalling and installing the plugin again I now get:

          java.lang.NullPointerException
          at org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.checkIfModified(AbstractTriggerByFullContext.java:55)
          at org.jenkinsci.lib.xtrigger.AbstractTrigger$Runner.run(AbstractTrigger.java:199)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
          at java.lang.Thread.run(Thread.java:722)

          notice that the line number in org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.checkIfModified is now reflecting the correct line in the latest xtrigger-lib ...

          Any feedback would be welcome.

          Show
          alex_ouzounis Alex Ouzounis added a comment - after uninstalling and installing the plugin again I now get: java.lang.NullPointerException at org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.checkIfModified(AbstractTriggerByFullContext.java:55) at org.jenkinsci.lib.xtrigger.AbstractTrigger$Runner.run(AbstractTrigger.java:199) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) notice that the line number in org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.checkIfModified is now reflecting the correct line in the latest xtrigger-lib ... Any feedback would be welcome.
          Hide
          alexhutton Alex Hutton added a comment -

          I had this also. I think it was from configuration data from the jenkins project not having been updated to a newer version of IvyTrigger. When I re-saved the IvyTrigger configuration from my affected projects this problem disappeared.

          Show
          alexhutton Alex Hutton added a comment - I had this also. I think it was from configuration data from the jenkins project not having been updated to a newer version of IvyTrigger. When I re-saved the IvyTrigger configuration from my affected projects this problem disappeared.
          Hide
          alex_ouzounis Alex Ouzounis added a comment - - edited

          Indeed. The problem is that as soon as you restart the Jenkins server it comes back again - so restarts happen only when really necessary.

          Tried to update to latest jenkins but got hit by another issue https://issues.jenkins-ci.org/browse/JENKINS-19796 so I had to go back to Jenkins 1.526

          Show
          alex_ouzounis Alex Ouzounis added a comment - - edited Indeed. The problem is that as soon as you restart the Jenkins server it comes back again - so restarts happen only when really necessary. Tried to update to latest jenkins but got hit by another issue https://issues.jenkins-ci.org/browse/JENKINS-19796 so I had to go back to Jenkins 1.526
          Hide
          alexhutton Alex Hutton added a comment -

          I just tried to restart Jenkins and I see, as you say, the problems returns.

          Show
          alexhutton Alex Hutton added a comment - I just tried to restart Jenkins and I see, as you say, the problems returns.
          Hide
          alex_ouzounis Alex Ouzounis added a comment - - edited

          The problem seems to be that on De-serialization, the transient variable lock get its Default value ie null.

          created pull request: https://github.com/jenkinsci/xtrigger-lib/pull/2 for a possible fix.

          Any feedback would be welcome.

          Show
          alex_ouzounis Alex Ouzounis added a comment - - edited The problem seems to be that on De-serialization, the transient variable lock get its Default value ie null. created pull request: https://github.com/jenkinsci/xtrigger-lib/pull/2 for a possible fix. Any feedback would be welcome.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              alex_ouzounis Alex Ouzounis
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: