Post job migration, the build is failing.

13 views

Skip to first unread message

Siddhesh Bhandarkar

unread,

Jan 23, 2017, 9:59:12 AM1/23/17

to Jenkins Users

Hi,

I have a job in the following sequence

Job 1 ----> Job2 --|----> Job 3 -----> Job 4
Job 5 ----> Job6 --|
Job 7 ----> Job8 --|

I have migrated all the jobs from my old machine to new machine. The Job 3 uses a recursive fan In on Job 2, Job 6 and Job 8. However, after migrating to the new environment, after completion of Job2 or Job6 or Job8, Job 3 does not start and I receive the following error.

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.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:1788)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:410)

I have migrated the Job fanin plugin as well as it shows as available and ticked on the Installed plugin list. Please advise me as to how I can solve the issue on the new box.

Victor Martinez

unread,

Jan 23, 2017, 11:56:22 AM1/23/17

to Jenkins Users

https://issues.jenkins-ci.org/browse/JENKINS-40151 might explain that issue and how to get fixed by upgrading that plugin