application version indication with git?

Question

In svn, we used to use post deployment hooks to write the deployed version checkin number as a build suffix for the application version deployed.

I.e. if we were deploying a 3.0 build of our app, the about window in the app would display 3.0.1234 where 1234 was the build revision from svn.

This allows QA to see a revision number and look at resolved bugs, comparing the build number in the resolved bugs, and if the deployed app's revision was higher than the one in the bug report, theyd be assured the fix was deployed (or not).

With git and mercurial, revision hashes dont provide similar features. How do u guys work around this using git?

score 1 · Answer 1 · answered Oct 26 '13 at 15:36

1

You could use a hook on tags in Git. Tags are made for versioning, among the others purposes.

You could even use the hash itself for versioning, see Debian for instance: a few packages have version strings like 4.8.5+git121-g2a9ea11. Why is it not OK?

answered Oct 26 '13 at 15:36

Stefano Sanfilippo

32,265
7
79
80

score 1 · Accepted Answer · answered Oct 26 '13 at 16:18

1

Use git describe. The output looks like this: v5.19.5-55-ga854082, a committish with three parts: v5.19.5 is the most recent tag in the current branch, 55 is the number of commits since this tag, and ga854082 is an abbreviated SHA1 with a preceding g. The number of commits may be used for checking if something is newer.

(The git describe output above is actually a real world example from the perl source code)

answered Oct 26 '13 at 16:18

Slaven Rezic

4,571
14
12

This sounds like the way to go since it counts how many revisions since the tag... that could be used as the "fixed changeset" value when resolving the bug, then used to compare with the one displayed by the application to indicate if the fix is deployed or not! – Rimer Oct 26 '13 at 16:27

score 0 · Answer 3 · answered Oct 26 '13 at 15:37

I use a post-checkout, post-commit, post-merge and post-rewrite hook with:

M=2228.1
rev=`git rev-parse --verify --short HEAD`

b=$(git branch --no-color 2> /dev/null | \
    sed -e '/^[^*]/d' -e 's/* \(.*\)/\1/')

case $b in
  (_tmp*)
        cnt=`git rev-list "$M"..$rev -- | wc -l`

        printf '#define AUTO_REVISION TEST%u+%s\n' "$cnt" "$rev" > auto-version.h
        ...
        ;;
  (*)
        cnt=`git rev-list $rev -- | wc -l`

        printf '#define AUTO_REVISION g%05u+%s\n' "$cnt" "$rev" > auto-version.h
        ...
        ;;
esac

cat << EOF >> auto-version.mk
AUTO_REVISION_CNT = $cnt
AUTO_REVISION_REV = $rev
EOF

The 'cnt' variable contains the number of commits since beginning or a certain branch/tag (2228.1 in this case) and depending on the actual branch (release/test) different schemes are applied.

application version indication with git?

3 Answers3