search

damianszczepanik / cucumber-reporting-jenkins

Java jenkins plugin for cucumber-jvm reporting
151 stars 12 forks source link

java.lang.NullPointerException #65

Closed onknows closed 9 years ago

onknows commented 11 years ago

I have been using plugin for one maybe two weeks. I was able to do around 40/50 builds succesfully

Now build runs fine but when I click on the link to see the report there is only a message saying java.lang.NullPointerException. Don't have a single clue on what is wrong. I was just adding steps from time to time.

Did I reach some limit? There are just two feature files, three scerario's, 15 steps or so per scenario. Not much.

I restarted Jenkins, reinstalled plugin, simplified the tests. It seems I have reached a final verdict of some sort.

I searched the internet for clues but there are no. This seems to be a new problem.

onknows commented 11 years ago

As it turns out, the nullpointer was caused by a pending step. So the workaround is to not have pending steps.

kingsleyh commented 11 years ago

ah yes - I will fix the pending step issue in the next release :)

--K

On 6 Jun 2013, at 20:55, Onno notifications@github.com wrote:

As it turns out, the nullpointer was caused by a pending step. So the workaround is to not have pending steps.

— Reply to this email directly or view it on GitHub.

raymondcg commented 11 years ago

+1 I got this issue as well.

sarnowski commented 11 years ago

some hints when this bugfix will be fixed?

kingsleyh commented 11 years ago

fixed in pending release

scophotog commented 11 years ago

This still in the works?

kingsleyh commented 11 years ago

Yeah - been busy adjusting to having a baby girl - full scale work will start again soon

Sent from my iPad

On 7 Oct 2013, at 16:08, Scott Argenziano notifications@github.com wrote:

This still in the works?

— Reply to this email directly or view it on GitHub.

plopez-bmj commented 10 years ago

A possible workaround until the bugfix is released is to add a post-build step in Jenkins that parses the Json files and turns the pending results into skipped results, before the report is generated (which happens in a later post-build step). Of course this will change the report a little bit, but you will be able to get rid of the exception, and pending/skipped are not the critical parts of it (at least not in my case).

Hope this helps to the impatient ones.

zoggo commented 10 years ago

Just incase it saves me putting the work around in place.. is this issue still on the agenda?

kingsleyh commented 10 years ago

Isn't this fixed in the latest released version?

Sent from my iPhone

On 6 Jun 2014, at 09:44, zoggo notifications@github.com wrote:

Just incase it saves me putting the work around in place.. is this issue still on the agenda?

— Reply to this email directly or view it on GitHub.

zoggo commented 10 years ago

Sorry, it is. I had upgraded the plug in on jenkins and then not restarted it. Looks great now, thanks!

On 06/06/2014 11:23, Kingsley Hendrickse wrote:

Isn't this fixed in the latest released version?

Sent from my iPhone

On 6 Jun 2014, at 09:44, zoggo notifications@github.com wrote:

Just incase it saves me putting the work around in place.. is this issue still on the agenda?

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java/issues/65#issuecomment-45322764.