Re: Automatically increment build number

[Mike Castle]

On Tue, May 08, 2001 at 04:04:34PM +0200, Weber, Mathias-Henry 1254 PPW-P1 
wrote:
> Another problem with coupling the incrementing of the counter to the build
> process would mean that this would have to be performed on every client
> host. The clients run Windows NT which is not my favourite choice for
> running script jobs. Furthermore the clients are rather differently equipped
> in terms of software the only common tool for script programming would be a
> DOS batch job. Do you understand that I am still interested in a different
> solution?


Just as a side note:  The CMD Batch stuff on NT is *nearly* as powerful as
Bourne shell.

A lot more cumbersome, but nearly as powerful.  Don't count is out so
quickly.

I did some scripting using Perforce's counter stuff, and NT's set /A to
increment the build number.

For something similar with cvs, you could probably keep a central area of
build numbers and either use watches on them and cvs edit or cvs admin to
enable an atomic update of the build number and so use cvs as your central
database.

Speaking of Perforce, what you want to do is basically a running counter of
all changes committed to the respository.  Perforce has such a thing built
in actually, called a change number.

If I was going to run a running counter like this, I'd probably use a 3rd
party database like PostgresQL.

mrc
-- 
       Mike Castle       Life is like a clock:  You can work constantly
  address@hidden  and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day.  -- mrc
    We are all of us living in the shadow of Manhattan.  -- Watchmen