Re: Continuous Integration and CVS

[Jim Hyslop]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Arthur Barrett wrote:
> Ben Rady,
>>Therefore, if Anthill creates a tag from it's 
>>working directory using 'cvs tag', the build 
>>artifacts created from the build can be perfectly 
>>reproduced by checking out that tag.
> 
> 
> Yes - in fact I avoid rtag because unless you can lock all the users out
> of the server there is potential to rtag a version you didn't intend to
> (because someone has committed a change).

I concur, Arthur. The safest way to mark a snapshot as "correct"
is to do a fresh checkout and 'cvs tag'.

> My own preference is to use a build system that is driven from the CM
> system (ie: build when changes are merged onto the build branch).
I sometimes wonder whether my style of working would screw this up :=)
When I check in changes, sometimes I separate the commits into several
commits, based on the specific changes made (all changes are usually
related in some way). If the automated system kicked in after the first
commit, the build may fail. Do you include some kind of delay to see if
there's another checkin within, say, two minutes of the first?

- --
Jim Hyslop
Dreampossible: Better software. Simply.     http://www.dreampossible.ca
                 Consulting * Mentoring * Training in
    C/C++ * OOD * SW Development & Practices * Version Management

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFET5zfLdDyDwyJw+MRAuIeAKCdlVvCyLaZIYhMx7ooUpKubLWCvQCg5h5i
QCxUrjz/dwFw+ZGEWv/BP3U=
=cqrB
-----END PGP SIGNATURE-----