This was one of my requirements of Owen when he began the migrate-to-git
project. We are using this method:
https://github.com/mixxxdj/mixxx/commit/73b918279d2b7525716dad9cd8e01a70dd8666e0#L2R69
See the latest builds:
http://builds.mixxx.org/builds/trunk/
http://builds.mixxx.org/builds/experimental-features_key/
gitXXXX is the revision number
The git version number is printed locally every time you run scons now:
http://builds.mixxx.org/jenkins/view/Trunk/job/mixxx-trunk-macosx/378/architecture=intel,os=macosx/console
"Building master - rev. 3453"
Just as in Bazaar, the revision numbers are not comparable across branches
so you need a branch:revision pair to be meaningful.
A helpful alias I have put in my gitconfig:
[alias]
revno = "!git log --pretty=oneline --first-parent | wc -l"
Cheers,
RJ
On Wed, Jun 19, 2013 at 2:46 AM, Daniel Schürmann <dasch...@mixxx.org>wrote:
> Hi
>
> while our GitHub move is proceeding fine, I miss hardly the consecutive
> revision number of Mixxx.
>
> Especially if we move ahead and release alpha test, every tester will
> hardly understand what is the difference between
>
>
> <https://github.com/mixxxdj/mixxx/commit/e1f6cd9f2e2a539ed2d675c1f0213821522585f0>e1f6cd9f2e
> and 87bcffbf9bb ...
> Or should he better test 17facf9bfe6?
>
> We can solve it with Jenkins, if we integrate the Jenkins build number,
> but that is not the same, because the number does not directly depends on
> the source itself and it is not reproachable for client builds.
>
> I have just found out, that GitHub actually has a consecutive revision
> number for every repro.
> You can query it using the Subversion api like that:
>
> svn info https://github.com/mixxxdj/mixxx/ | sed -ne 's/^Revision: //p'
>
> Compared to the Bazaar revno, which was unique for a single branch, the
> Subversion Revision Number is unique for the whole repository.
>
> Unfortunately (as far as I understand) this number can only queried
> directly from GitHub and is not included in a local git clone. So it looks
> like this is unhandy for our approach.
>
> So what do you think, Is this number a suitable replacement for bzr revno?
> Is there a smart way to include this number in our target builds. Can we
> use git hooks for this job?
> Or is there a better Idea?
>
> https://bugs.launchpad.net/mixxx/+bug/1192288
>
> Kind regards
>
> Daniel
>
>
>
>
>
>
>
>
> <https://github.com/mixxxdj/mixxx/commit/e1f6cd9f2e2a539ed2d675c1f0213821522585f0>
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org
>
>
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
