Difference between revisions of "HudsonAndOtherPlugins"

From CitconWiki
Jump to navigationJump to search
(finally fix the link)
Line 13: Line 13:
  
 
Hudson plugins we wish we had:
 
Hudson plugins we wish we had:
* Dependency graph showing which jobs trigger which other jobs [https://hudson.dev.java.net/issues/show_bug.cgi?id=4321 Hudson issue 4321)
+
* Dependency graph showing which jobs trigger which other jobs [https://hudson.dev.java.net/issues/show_bug.cgi?id=4321 Hudson issue 4321]
 
* [http://www.gridgain.com/ GridGain] integration (farms work out to multiple machines and JVMs as if in a single JVM)
 
* [http://www.gridgain.com/ GridGain] integration (farms work out to multiple machines and JVMs as if in a single JVM)
 
* Detect slave configuration and auto-tag and group (all Windows machines, all machines with over 1GB RAM)
 
* Detect slave configuration and auto-tag and group (all Windows machines, all machines with over 1GB RAM)

Revision as of 10:04, 24 September 2009

Great things about Hudson plugins:

Not so great things about Hudson plugins:

  • Can be hard to figure out where you should plug in for your particular task
  • Jelly difficult to work with - have to know just where to put your file
  • Community (including Kohsuke) are not Maven experts, so:
  • Some plugins are version-locked to Hudson core version - break if you update Hudson

Hudson plugins we wish we had:

  • Dependency graph showing which jobs trigger which other jobs Hudson issue 4321
  • GridGain integration (farms work out to multiple machines and JVMs as if in a single JVM)
  • Detect slave configuration and auto-tag and group (all Windows machines, all machines with over 1GB RAM)
  • Show timestamps in online console output, or even better, provide timings for each action (helps with performance-tuning your jobs)

Other tools:

Free help on offer from Douglas_Squirrel