On Mon, Dec 09, 2002 at 06:51:22PM -0800, Noel Yap wrote:
>
> A good portion of the build breakage is due to
> developers forgetting to checkin a file, most likely a
> new file they forgot to add to begin with. So, the
> tests will work within their environment, but will
> still break others' builds. I guess this doesn't
> happen too often where you are?
these sorts of problems are solvable using some combination
of tools and conventions.
it's easy to write a script in your favorite scripting language
that will (1) check for "?" (uncontrolled) files, (2) display the
names of those files, and (3) give you the option of (a) just commiting,
(b) adding the files first and then commiting, (c) deleting the files,
(d) adding the files to the "ignores" list, or (e) just not committing.
likewise you can create a "commit" target in your build script that will
build first (and run unit tests if you have them) and then commit only
if the build/tests were successful.
then you just have to get people to use these tools instead of doing
commits directly.
if you have uncooperative developers, that's another story. but then
it's not even so much of a process problem as it is a people problem.
-brian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 10 22:14:27 2002