Difference between revisions of "HudsonAndOtherPlugins"

From CitconWiki
Jump to navigationJump to search
m
 
Line 6: Line 6:
 
Not so 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
 
* Can be hard to figure out where you should plug in for your particular task
** [http://wiki.hudson-ci.org/display/HUDSON/Extension+points]
+
** [http://wiki.hudson-ci.org/display/HUDSON/Extension+points list of extension points]
 
* [http://commons.apache.org/jelly/ Jelly] difficult to work with - have to know just where to put your file
 
* [http://commons.apache.org/jelly/ Jelly] difficult to work with - have to know just where to put your file
 
* Community (including Kohsuke) are not Maven experts, so:
 
* Community (including Kohsuke) are not Maven experts, so:

Latest revision as of 10:25, 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
  • 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