Details

    • Similar Issues:

      Description

      We use JIRA triggers a lot in our environment and today we had following exception:

      java.lang.NullPointerException: Cannot get property 'fullName' on null object
       at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:60)
       at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:172)
       at org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java:47)
       at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:296)
       at com.ceilfors.jenkins.plugins.jiratrigger.JiraTrigger$JiraTriggerDescriptor.removeTrigger(JiraTrigger.groovy:146)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:498)
      

      It seems there is no guaranty JiraTrigger will always have a job attached to it.

      I've already created a pull request at https://github.com/jenkinsci/jira-trigger-plugin/pull/1 to rectify that problem.

      I'm not sure  why that happened in the first place. After I applied that fix from the pull request mentioned above, I stopped seeing JiraTriggers without a job.

      Waldemar

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                ceilfors Wisen Tanasa
                Reporter:
                wzurowski Waldemar Zurowski
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: