Today I’ll be releasing nightly RPMs from Chef master in an attempt to
do some kind of CI/testing of the RBEL RPM packages. This will help me
to anticipate changes/breakage and release packages in a couple of
days (maybe even the same day) after the official Opscode Chef
I’ve got the build/CI system in place and now I’m writing some tests
to validate the build.
I have a question related to the build:
RPMs are time-stamped when they’re built (i.e.
rubygem-chef-0.10.2-3.20110725_1130.el6.noarch.rpm) but I haven’t
found a good way of time stamping chef gems other than modifying
lib/*/version.rb in every chef module on the fly.
Is there a better way of doing this kind of stuff?
I’m thinking of appending git short commit string to the VERSION
string or something like that, so I can validate the build is up2date
and the version string appears in Chef webui.
Feedback is greatly appreciated.