Googlielmo's blog

It's a good practice for a Jenkins administrator to check for installed plugins usage before updating one of them or to understand if some isn't used any more and can be uninstalled. The Enterprise Jenkins release provides a plugin ( http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-features-plugin-usage-plugin.cb ) that shows in a tabular form the usage of the installed plugins across the different jobs in a Jenkins instance. It is a really simple but extremely helpful plugin. But how could you do the same if no Enterprise Jenkins is available for you? The same functionality can be implemented with a quite simple Groovy script using the Jenkins classes only. This script can be executed from the Jenkins script console (accessible from Manage Jenkins -> Script Console ). Here's the code explained step by step. For a better understanding of this post I suggest you have the basics about the Jenkins model and the Jenkins Java classes. First of all we need to get all

This year the Jenkins User Conference will touch Europe in Berlin on June 25th. Here's the agenda: http://www.cloudbees.com/jenkins/juc-2014/berlin As a Jenkins user in a CI/CD context, a plugin developer and a SVT automation engineer I will attend this event, of course. I hope to meet there in Berlin some of the readers of this blog. Cheers.

If you like me are an espresso coffee lover (the real espresso, http://en.wikipedia.org/wiki/Espresso , not that sort of dark filthy water imitation you can find in many american coffee bars) you should recognize the object in figure 1: Fig. 1 - The traditional Moka It is a Moka machine from a famous Italian brand. It allows you to prepare just espresso coffee, but it does its job very well. Some other coffee machine producers got some other ideas to add features to this basic but brilliant concept. Here an example: Fig. 2 - Advanced Moka If you are an espesso lover and a lazy guy too you should appreciate it. The producer of the advanced moka shown in figure 2 implemented the following: Scheduling: you can program the exact time to have the coffee ready to be consumed. Validation: Before starting the Moka checks if coffee and water were provided. If not, it warns the user with human readable messages. Automation: the moka itself manages the preparation (no hum