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

JobFanIn plugin "FATAL: null java.lang.NullPointerException"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • job-fan-in-plugin
    • None
    • Build
      Jenkins: Jenkins ver. 2.10
      Java Version: "1.7.0_09-icedtea"
      OS : Windows7
      apache-tomcat-7.0.61
      job-fan-in-plugin 1.1.2

      Hi Team,

      I am facing FATAL: null java.lang.NullPointerException error during build.

      I have a configuration of jobfenin plugin where I want to make sure all mapped job in fanin plugin execute first. I have 10 jobs which has to build first and all the job are getting built successfully but jobfanin plugin is not working as expected. I am getting below error in one of the job.

      FATAL: null
      java.lang.NullPointerException
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.isNotBuildingAndStable(FanInReverseBuildTrigger.java:229)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:204)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.thisAndUpstreamAreNotBuildingAndStable(FanInReverseBuildTrigger.java:210)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.allUpsteamIsBuild(FanInReverseBuildTrigger.java:186)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger.access$300(FanInReverseBuildTrigger.java:62)
      at org.lonkar.jobfanin.FanInReverseBuildTrigger$1.shouldTriggerBuild(FanInReverseBuildTrigger.java:249)
      at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:246)
      at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:681)
      at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
      at hudson.model.Run.execute(Run.java:1767)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:98)
      at hudson.model.Executor.run(Executor.java:410)

      Which might be restricting the job to trigger.

      Please help resolve this issue

        1. config.doc
          38 kB

          [JENKINS-40151] JobFanIn plugin "FATAL: null java.lang.NullPointerException"

          Yogesh Lonkar added a comment - - edited

          Fixed in *https://github.com/jenkinsci/job-fan-in-plugin/releases/tag/job-fan-in-1.1.3*. Will be available after next plugin repository refresh

          Yogesh Lonkar added a comment - - edited Fixed in * https://github.com/jenkinsci/job-fan-in-plugin/releases/tag/job-fan-in-1.1.3* . Will be available after next plugin repository refresh

          rajendra rawat added a comment -

          That error is message is not occurring any more but the original issue remains there. My fanin plugin is not working. I have configured 10 jobs which should execute first successfully and it is happening but my job having fanin configuration is not getting called. I have to trigger it manually.

          Kindly suggest what could be the causing this issue.

          rajendra rawat added a comment - That error is message is not occurring any more but the original issue remains there. My fanin plugin is not working. I have configured 10 jobs which should execute first successfully and it is happening but my job having fanin configuration is not getting called. I have to trigger it manually. Kindly suggest what could be the causing this issue.

          rajendra rawat added a comment -

          Jobs are given in format below

          A,B,C,D,E,F,G,H,I,J,K,L

          rajendra rawat added a comment - Jobs are given in format below A,B,C,D,E,F,G,H,I,J,K,L

          Yogesh Lonkar added a comment -

          The issue might be with any of above jobs. If any of these are never build or has last successful build you will not get trigger, To debugg the issue what i can suggest is start with Limited jobs such as 'A,B,C' and keep on adding more jobs to configuration and check if trigger is working, because I don't see any other reason for trigger to fail. BTW I assume instead of "A,B,C,D,E,F,G,H,I,J,K,L" you have actual Job Id's

          Yogesh Lonkar added a comment - The issue might be with any of above jobs. If any of these are never build or has last successful build you will not get trigger, To debugg the issue what i can suggest is start with Limited jobs such as 'A,B,C' and keep on adding more jobs to configuration and check if trigger is working, because I don't see any other reason for trigger to fail. BTW I assume instead of "A,B,C,D,E,F,G,H,I,J,K,L" you have actual Job Id's

          rajendra rawat added a comment -

          Yes, A,B,C .... are just for example, I have given actual jobs name in fanin configuration..
          I have tried it with single job but still fanin is not working. single job i.e A has built successfully but fanin have not called.

          rajendra rawat added a comment - Yes, A,B,C .... are just for example, I have given actual jobs name in fanin configuration.. I have tried it with single job but still fanin is not working. single job i.e A has built successfully but fanin have not called.

          rajendra rawat added a comment -

          Single job is getting called if I un check "Watch upstream projects recursively " checkbox.

          so do I need to uncheck "Watch upstream projects recursively " for all the jobs and try?
          Kindly tell me the purpose of "Watch upstream projects recursively "

          rajendra rawat added a comment - Single job is getting called if I un check "Watch upstream projects recursively " checkbox. so do I need to uncheck "Watch upstream projects recursively " for all the jobs and try? Kindly tell me the purpose of "Watch upstream projects recursively "

          Yogesh Lonkar added a comment -

          Not sure how I can help here, Can you post your configuration, related logs that you can see.

          Yogesh Lonkar added a comment - Not sure how I can help here, Can you post your configuration, related logs that you can see.

          rajendra rawat added a comment -

          I just tried adding another job without checking "Watch upstream projects recursively".
          what i did is as below.

          there are two jobs mapped now A,B. I just triggered A and have not triggered B.
          A built successfully and fanin job gets called. It should have not happened as job B was not triggered.

          rajendra rawat added a comment - I just tried adding another job without checking "Watch upstream projects recursively". what i did is as below. there are two jobs mapped now A,B. I just triggered A and have not triggered B. A built successfully and fanin job gets called. It should have not happened as job B was not triggered.

          Yogesh Lonkar added a comment -

          If B is not In Queue and it's last build was successful, then trigger will happen. Because this plugin can't check if B was not executed after A

          Yogesh Lonkar added a comment - If B is not In Queue and it's last build was successful, then trigger will happen. Because this plugin can't check if B was not executed after A

          rajendra rawat added a comment -

          I have attached fanin config screenshot with config.doc file

          rajendra rawat added a comment - I have attached fanin config screenshot with config.doc file

            lonkaryogeshr Yogesh Lonkar
            rajendra_rawat17 rajendra rawat
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: