Giacomo Vacca

The other day I was browsing the slides of "Continuous Deployment with Jenkins" , from PuppetLabs . One sentence in particular I found relevant for what I was doing, and important in general: Puppet manifests are code too. To be honest, I don't think I need to sale this very hard, so I'll proceed to a practical consequence: unit testing for puppet modules . Unsurprisingly, there's a app tool for that: rspec-puppet . At least this is what I've been using for some time and find very useful and easy to use. I've even created some Jenkins jobs just to unit test Puppet modules. You can find a tutorial for rspec-puppet here . Feel free to leave this article, read the tutorial, experiment a little and come back later. What I wanted to share is some tricks/settings that I had to use, which I haven't found in one single place so far. As you can see in the tutorial, rspec-puppet generates a dir skeleton for you (with the command 'rspec-puppet in...

Problem: "I want to get the git tag of the current project, but only if it's associated to the latest commit. If not, I want to know what's the current commit hash." In order to achieve this I was using something like: This works but a drawback is that I either see the tag or the latest commit. So a coworker pointed me to this: git describe --tags --always which I didn't know and it's just great. It returns a string with this format: TAG-N-gSHA where: TAG is the most recent tag. N is the number of commits from the TAG. 'g' is just a formatting convention. SHA is the latest commit (HEAD). If the latest commit is also pointed by the tag, then it just returns TAG. 'git describe' is explained here .