Difference between revisions of "HudsonAndOtherPlugins"
From CitconWiki
Jump to navigationJump to search| Line 1: | Line 1: | ||
Great things about Hudson plugins: | Great things about Hudson plugins: | ||
* Maven makes it easy to start | * Maven makes it easy to start | ||
| − | * [http://www.java.net/blogs/kohsuke/ | + | * [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 | * [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 | ||
Revision as of 07:35, 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 abstractions tend to leak () and hard to
Hudson plugins we wish we had:
- Dependency graph showing which jobs start which other jobs
- Grid Gain 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 >1GB RAM)
- Show timestamps in online console output, or even better, provide timings for each action (helps with performance-tuning your jobs)
