Move GIT revision number to build script (Trac #419)

[sasview-bot]

The command to fetch the GIT revision number must be put into the build script for all builds. I will send the appropriate information to Torben to be changed for the next revision.

Migrated from http://trac.sasview.org/ticket/419

{
    "status": "closed",
    "changetime": "2016-10-06T15:48:51",
    "_ts": "2016-10-06 15:48:51.108054+00:00",
    "description": "The command to fetch the GIT revision number must be put into the build script for all builds. I will send the appropriate information to Torben to be changed for the next revision.",
    "reporter": "krzywon",
    "cc": "",
    "resolution": "fixed",
    "workpackage": "SasView Framework Enhancements",
    "time": "2015-05-19T14:13:22",
    "component": "SasView",
    "summary": "Move GIT revision number to build script",
    "priority": "minor",
    "keywords": "",
    "milestone": "SasView 4.1.0",
    "owner": "wojciech",
    "type": "defect"
}

[butlerpd]

Trac update at 2015/06/21 21:50:16: butler changed workpackage from "SasView Bug Fixing" to "SasView Framework Enhancements"

[butlerpd]

Trac update at 2015/08/14 20:13:19: butler changed milestone from "SasView Next Release +1" to "SasView 4.0.0"

[ajj]

Trac update at 2016/02/28 11:27:07:

• ajj commented:

Was the info sent to Torben?

• ajj changed owner from "" to "trnielsen"
• ajj changed status from "new" to "assigned"

[butlerpd]

Trac update at 2016/03/06 18:56:41:

• butler commented:

Jeff should work with Torben on this as necessary -- I think he had it working locally but needed to make the change on the build machine as I recall. Also in spirit of disciplined and professional it really is time to get this done so moving it to critical list (can't call it blocker as is not really part of original core tasks we set out for this release).

• butler changed priority from "minor" to "critical"

[sasview-bot]

Trac update at 2016/03/20 10:22:31: krzywon commented:

http://stackoverflow.com/questions/5581722/how-can-i-rewrite-python-version-with-git

Here is a quick overview of how to do this during the build.

[butlerpd]

Trac update at 2016/06/19 15:03:56: butler commented:

Note that we need to use

git describe --tags

as the last annotated tag was version 3.0.0 which will make the version number look wrong. Of course that means we should be annotating our release tags with a -a option on the tag. However we should also not assume that all future tags will be properly annotated and the --tags option is most appropriate anyway.