[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Automatically increment build number

From: Todd Denniston
Subject: Re: Automatically increment build number
Date: Wed, 09 May 2001 09:42:03 -0500

"Weber, Mathias-Henry 1254 PPW-P1" wrote:
> Again - you're absolutely correct. This is what I do for "real" releases
> (linking features to a tag). I just wanted to have some kind of a compact
> handle that help me to gauge the behaviour of the various intermediate test
> releases that come up during the same day and sometimes reside
> simultaneously on the same dedicated test machine with names like
>         Appl.exe
>         Appl.exe.old
>         Appl.exe.bak
>         Appl.exe.debug
>         etc.
> The process is that a developer builds an intermediate executable on his
> personal machine including some fresh features that he wants to test. Then
> he takes this executable to the dedicated test machine (there is special
> hardware needed to test). Here he finds the above depicted situation and he
> needs to copy the new executable to the test machine with the name
> "Appl.exe".
> So - he moves the existing "Appl.exe" to something like
> "Appl.exe.dontknowhowtoname" and copies his file in place. After having
> tested he leaves the test machine and checks in his modifications.
> We build "official" test releases about once a week, and there is a tag and
> a release notes file coming with each of them. But we daily build several
> "personal" releases and it does not pay off to document each of these
> releases mainly bound to trash can. Here a build number that is incremented
> automatically would be handy.
> Since this topic is in no way crucial I consider this thread closed.
> Nevertheless it helped me a lot to discuss it here to get a clearer view of
> it.
> Thanks
> Mathias

Sorry to reopen but I could not help but to believe the restated problem
(tracking where something is in one day / builder) as a little easier to

1. have your "official" test release tag script apply appropriate strings for
an "official" release.
2. have another tag script set the development baseline up with a line like
the following:
fprintf(stderr, "\n \t compiled %s %s\n", __DATE__ , __TIME__ );

It should also be possible to some how pass in the username (on unix anyway)
as a -D option to the compiler and add that to the line.

Todd Denniston, Code 6067, NSWC Crane mailto:address@hidden
I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb.  Thank you.
        -- Vance Petree, Virginia Power

reply via email to

[Prev in Thread] Current Thread [Next in Thread]