-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stats and notes output is not being published #5
Comments
curiously after messing around with different configuration settings for ... well its been quite a while, on the same day I took the time to submit an issue on this problem, they're now working in the most recent build. So what changed? I went to try a different Ruby Metrics plugin (http://blog.josephwilk.net/ruby/ruby-metric-fu-hudson-plugin.html) and in the process I installed version 1.5.1 of the metric_fu gem, which installed a bunch of metrics related gems. My hunch is that one the gems installed during this process is a hidden dependency of this Jenkins plugin. |
Experiencing the same problem. I added the metric_fu gem to my Gemfile, but that didn't resolve the issue. |
This plugin is unrelated to metric_fu. Right now, you can run metric_fu after your build and use the html publisher to archive reports. See https://github.com/metricfu/metric_fu |
I'm experiencing this same issue right now. Have you guys found a solution ? |
Y'all will need to post more info about your configuration. |
I'm perfectly OK with that but I don't know exactly what to post. What would throw a little light on the problem ? |
i've tried a variety of different configurations and i'm not able to get either the stats of notes options to produce any output to the build.
i do get output back from flog and rcov; however the flog output does not look right to me.
Despite seeing the following in my console output:
Publishing rails notes report...
Publishing rails stats report...
Sending e-mails to: [email protected]
Finished: SUCCESS
--> No valid coverage data available
The text was updated successfully, but these errors were encountered: