Similar to the post about Eclipse’s plugins, now I would like to share my recommendation about Hudson’s plugins (the most simple ones) .
(Why Hudson renamed to Jenkins : see at either InfoQ or The Register)
.
.
Build wrappers
Build-timeout is simple but neccessary:
https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin
Mask password on console:
https://wiki.jenkins-ci.org/display/JENKINS/Mask+Passwords+Plugin
If running on Linux/Unix server, this one can provide a lightweight X server:
https://wiki.jenkins-ci.org/display/JENKINS/Xvnc+Plugin
SSH connection is also popular in the *nix world:
https://wiki.jenkins-ci.org/display/JENKINS/SSH+plugin
.
Build notifiers
An extension of the built-in email feature is enough:
https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
.
Source code version control
Subversion (built-in), Git, Mercurial are all good. If you have already have a ViewVC installation, use ViewVC plugin:
https://wiki.jenkins-ci.org/display/JENKINS/ViewVC+Plugin
If you want to keep the change log of recent builds, but also want to save space by discarding old builds:
https://wiki.jenkins-ci.org/display/JENKINS/Change+Log+History+Plugin
.
Build triggers
The inbuilt triggers are enough, I think. There are downstream/upstream, shell scripts, env vars, … Maybe sometimes you may need this one:
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin
Another useful plugin for locking some jobs while building one:
https://wiki.jenkins-ci.org/display/JENKINS/Locks+and+Latches+plugin
.
Build tools
Well, for Java geeks there are Ant and Maven plugins. There are also others like Gant, Gradle, Rake, Python, PowerShell plugins… but there is also a small plugin which can be useful at times:
https://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin
.
Build reports
Well, the well-known static analysis tools like Cobertura, PMD/Checkstyle/FireBugs plugins . There is one for TestNG too :
https://wiki.jenkins-ci.org/display/JENKINS/testng-plugin
.
External site/tool integrations
To name a few: Redmine, Trac, JIRA, Bugzilla, Mantis, Sonar
, Firefox, Android, GitHub, GoogleCode… Hmmm, just pick what you are using, don’t try to get it all cuz it’s time to K.I.S.S !
.
UI plugins
Some are quite fun: Green Balls, Chuck Noris, Girls. The Description Setter is useful to quickly extract infor (version, etc…) and display them in the build description:
https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin
.
That’s enough, I think. Not too much, huh ? Well, after 2 years using Hudson I find myself never use more than 10 plugins at once (for 20 build-jobs or so) . Depending on the requirements, one can install more plugins to achieve it, not the other way around IMHO.
There are more… You may want to try ’em out yourself !
./.
Pingback: SVN best practices | DucQuoc's Blog
Usually I do not read post on blogs, but I would like to say that this write-up very pressured me to take a look at and do it! Your writing taste has been amazed me. Thanks, very great article.
Thanks. I’ll try to keep the posts succint and still informative :-) .
Pingback: Why Maven 3 | DucQuoc's Blog
Thank you for the information! Have you tried Jenkins plugin from Blazemeter?
http://community.blazemeter.com/knowledgebase/articles/102721-blazemeter-plugin-to-jenkins
It allows to create perfarmance test task as a post-build job.
Pingback: Logging best practices | DucQuoc's Blog
Pingback: Firefox over Chrome? | DucQuoc's Blog