Fixed it luckily. I upgraded Jenkins, downgraded batch task and removed the envfile. Don't ask me what was causing the NPE. Haven't had time yet to search the root cause.
ciya Am Mittwoch, 9. Mai 2012 10:39:53 UTC+2 schrieb Jan Seidel: > > *DOH!* Oh great, > > I am in the middle of an migration, plus creating new softwarebranches > today as requested and have to build a huge project in a few hours as well. > I was doing some build testing to be on the safe side that at least the > build process runs smooth and learned pretty quick that the jobs ain't > working anymore. > ALL of them, modified and unmodified. > > The build status instantly turns to failure but no log output at all. > Looking into the Jenkins log files reveals: > > > *May 9, 2012 10:31:13 AM hudson.model.Executor run > SEVERE: Executor threw an exception > java.lang.NullPointerException: Current Project is null > at > com.sonyericsson.rebuild.RebuildAction.getProject(RebuildAction.java:117) > at > com.sonyericsson.rebuild.RebuildAction.getUrlName(RebuildAction.java:144) > at > org.jenkinsci.lib.envinject.service.EnvInjectActionRetriever.getEnvInjectAction(EnvInjectActionRetriever.java:32) > at > org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:51) > at hudson.plugins.batch_task.BatchRun.run(BatchRun.java:224) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:238)* > > Does someone have a clue about this? I am in serious trouble and running out > of time right now -.- > > Cheers > Jan > > >
