Difference between revisions of "HudsonAndOtherPlugins"
From CitconWiki
Jump to navigationJump to searchm |
|||
| (10 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | Great things about Hudson plugins: | ||
| + | * [http://maven.apache.org/ Maven] makes it easy to start | ||
| + | * [http://www.java.net/blogs/kohsuke/ Kohsuke] is really helpful and the [https://hudson.dev.java.net/mailing-lists.html Hudson developers' mailing list] is an excellent resource | ||
| + | * [http://wiki.hudson-ci.org/display/HUDSON/Extend+Hudson Hudson wiki] has good plugin guides (if slightly out of date) and you can update them | ||
| + | |||
| + | Not so great things about Hudson plugins: | ||
| + | * Can be hard to figure out where you should plug in for your particular task | ||
| + | ** [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 | ||
| + | * Community (including Kohsuke) are not Maven experts, so: | ||
| + | ** can be hard to debug and fix [http://www.joelonsoftware.com/articles/LeakyAbstractions.html leaky abstractions] | ||
| + | ** creating your pom.xml is hit-and-miss | ||
| + | * Some plugins are version-locked to Hudson core version - break if you update Hudson | ||
| + | |||
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] | ||
| + | * [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) | ||
| + | ** [http://wiki.hudson-ci.org/display/HUDSON/PlatformLabeler+Plugin See PlatformLabeler Hudson plugin] | ||
| + | * Show timestamps in online console output, or even better, provide timings for each action (helps with performance-tuning your jobs) | ||
| + | ** [https://hudson.dev.java.net/issues/show_bug.cgi?id=2137 Hudson issue 2137] | ||
| − | + | Other tools: | |
| − | * | + | * [http://www.jetbrains.com/teamcity/ TeamCity] also has plugins |
| − | * | + | * [http://studios.thoughtworks.com/cruise-release-management/features-benefits Cruise], [http://www-01.ibm.com/software/awdtools/buildforge/ BuildForge] don't seem to |
| − | + | ||
| + | Free help on offer from [[Douglas_Squirrel]] | ||
Latest revision as of 11:25, 24 September 2009
Great things about Hudson plugins:
- Maven makes it easy to start
- Kohsuke is really helpful and the Hudson developers' mailing list is an excellent resource
- Hudson wiki has good plugin guides (if slightly out of date) and you can update them
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:
- can be hard to debug and fix leaky abstractions
- creating your pom.xml is hit-and-miss
- 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:
- TeamCity also has plugins
- Cruise, BuildForge don't seem to
Free help on offer from Douglas_Squirrel
