Adding other tools support in Hudson's rubyMetrics plugin

Posted in Original Content by David Cavalero - last update: Dec 28, 2023

If you arrive on this page - you were probably following a link. This page was created by David Cavalera, who no longer owns this domain. It is still linked/indexed - so I decided to keep it online You can find David on Twitter/X or LinkedIn

Original version of this page can still be found on the internet archive.

<Original content below:>

Ok, I have to admit it, I’m a lazy, but a good lazy, like my good friend Sergio says. I like to work as less as possible and this days while I wrote the new Flog support in the Hudson’s rubyMetrics plugin I realized that I didn’t want to copy the same code over and over again anymore.

So, I just added to the repository a ruby script to generate the basic skeleton for add every other tool support to the plugin. The script asks some questions and it generates basic classes that it needs to add support for that tool.

Still here? what are you waiting to add your favorite tool support to the plugin? You just need to follow this few steps:

1 Check the code out:

$ svn co https://svn.dev.java.net/svn/hudson/trunk/hudson/plugins/rubyMetrics

or

$ git clone git://github.com/calavera/rubyMetrics.git

2 Run the script:

$ ruby src/main/ruby/generator.rb

3 Go to the Publisher class

and complete the perform method and go to the BuildAction view and complete the jelly template. Psss rcov, flog, rails stats or rails notes support can help you.

4 Test the plugin using maven#

it launches a dedicated instance of hudson :S

$ mvn hpi:run

5 File a ticket in hudson’s jira

to the component RubyMetrics and attach your patch.

Btw, if you didn’t notice yet, I set up a mirror of the project in github. Enjoy it.

<End or original content>

Other articles