Code changed in jenkins
User: Gregory Boissinot
Path:
pom.xml
http://jenkins-ci.org/commit/fstrigger-plugin/088eb20079c22f68e45551c3aaeae8a3b28f7a96
Log:
Fix JENKINS-16809

–
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

It is a FSTrigger issue through its embedded 'envinject-lib' librarry.
The issue might become with new Jenkins versions.
I try a fix by updating to latest envinject library.
Please try the new fstrigger jenkins version (0.35).

Thanks! Where can I find the 0.35 release? It's not showing up in the Jenkins updates list, nor here http://updates.jenkins-ci.org/download/plugins/fstrigger/

I'm sorry there was an issue on the release process.
For now, it is OK.
You can download it manually at the following URL
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/fstrigger/0.35/fstrigger-0.35.hpi

Hi Gregory,
Installed the latest fix. The original NPE is gone, but now I get a new exception during job-loading:

Feb 18, 2013 1:01:45 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading job Eval-Hot-Systemtest
java.lang.NullPointerException: Current Project is null
at com.sonyericsson.rebuild.RebuildAction.getProject(RebuildAction.java:138)
at com.sonyericsson.rebuild.RebuildAction.isRebuildAvailable(RebuildAction.java:276)
at com.sonyericsson.rebuild.RebuildAction.getUrlName(RebuildAction.java:163)
at org.jenkinsci.lib.envinject.service.EnvInjectActionRetriever.getEnvInjectAction(EnvInjectActionRetriever.java:36)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:54)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getPollingEnvVars(EnvVarsResolver.java:36)
at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.start(FolderContentTrigger.java:371)
at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:97)
at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26)
at hudson.model.AbstractProject.onLoad(AbstractProject.java:294)
at hudson.model.Project.onLoad(Project.java:83)
at hudson.model.Items.load(Items.java:221)
at jenkins.model.Jenkins$17.run(Jenkins.java:2539)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:883)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)

Still about the same fstrigger jobs, which haven't changed. Today, I'm using Jenkins v1.502.

Hi Riccardo,
Thanks for your comment.
If you look at the stack trace, you see the bug relies on the rebuild plugin from SonyEricsson.
Rebuild plugin embeds the envinject library. There is a bug in the current version used by the rebuild plugin.
Please report a new bug for the rebuild plugin and ask to upgrade to envinject-lib 1.16.