Broken release build and git revision numbers

[Justin Mclean <ju...@classsoftware.com>]

Hi,

When we were using SVN the SVN revision number was used in various places. This needs to be a number (so hashes are out) and may need to be numerically increasing ie current number bigger than last number (not 100% on that).

This effects:
- Version numbers in framework XML description files. eg flex-config.xml.
- Version.as files in the SDK.
- Names of framework RSL files.

For now I'm going to do this:

        <tstamp>
        	<format property="build.number.date" pattern="yyyyMMdd" />
        </tstamp>

ie set the build number to the current date.


Can any Git experts please comment if there an alternative to doing this this way.

Do any IDEs use the build number form the config is any way that may be broken by this approach?

Can anyone see any issue (even minor) with this approach? 

This is a major change to how the SDK is builds, configures and names things so could have subtle and unknown side effects.

Thanks,
Justin

RE: Broken release build and git revision numbers

["Michael A. Labriola" <la...@digitalprimates.net>]

>Can any Git experts please comment if there an alternative to doing this this way.

If you have a moment, take a look at git describe as an idea. It basically gives you the latest tag and a number of commits since then and a hash. Its not a simple sequence, but see if it helps.

This one is okay.

http://alblue.bandlem.com/2010/11/automatically-tagging-builds-with-git.html

Read Me:

http://git-scm.com/book/en/Distributed-Git-Maintaining-a-Project#Generating-a-Build-Number

Re: Broken release build and git revision numbers

[Justin Mclean <ju...@classsoftware.com>]

HI,

The one minor down side is that it's now it harder to tell exactly where a SDK was build from (no revision number n flex-describtion.xml). There would be a branch with the same version number so it's a minor annoyance.

Justin