This is a continuation of my mumblings about useful Jenkins plugins (see the first post here: http://kaczanowscy.pl/tomek/2012-05/recommended-jenkins-plugins). As we progress towards continuous delivery I learn a lot about new plugins.

Today I would like to present few more plugins, which are really, really helpful:

• TextFinder Plugin, http://wiki.jenkins-ci.org/display/JENKINS/Text-finder+Plugin - useful when you do something outside Maven, and you need to e.g. tell Jenkins to mark build as FAILED if some error appears in log files. We use it to verify our deployments (well, there is more to it, but the first check is by browsing the logs).
• Build Timeout Plugin, http://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin - when your builds have a tendency to hang forever this plugin can kill them after specified time (see also https://wiki.jenkins-ci.org/display/JENKINS/Build+is+hanging). But I consider using it as a last resort, unless a better solution is found (in short it helps to fight the symptoms but does not cure the situation).
• Maven Release Plugin, http://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin - if you live in Maven world you will need this one. BTW. I have to admit that in the past I used this plugin a lot, but now we do not release so often ("release", in a Maven sense) so it's less helpful.
• HTML Publisher Plugin, https://wiki.jenkins-ci.org/display/JENKINS/HTML+Publisher+Plugin Allows to add links to arbitrary files (e.g. selenium test reports) so they are visible on job's page.,

The next post will be related much more to building pipelines. But for now that would be it. Bye!