[Top][All Lists]

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

Build environments using CVS

From: Brian Blignaut
Subject: Build environments using CVS
Date: Wed, 20 Oct 2004 15:08:38 +0100


Firstly let me say that if this is not the appropriate place to ask this question I apologize, I am just not sure where else to post. I am trying to setup a build process that works with CVS tags and am having a bit of a problem.

The Build Environment

1. Development - developer’s adding/changing/fixing code
2. Testing - with software testers, and test data – TEST tag
3. Release - Software built for release to client – LIVE tag

The Problem


Deleting files from CVS retains the TEST, LIVE tags.  As a result the files that not meant to be built are being included in TEST, LIVE builds.

The Details

What I am trying to achieve is the ability to prevent files from entering the “Testing” and hence “Release” phases. So developers can make changes to existing source files and be confident that their changes will not be built into the “Testing” and “Release” phases until they are satisfied with the changes.

The problem I am having is that when files are deleted, they still retain their TEST or LIVE tags and as such are updated in to the “Testing” and “Release” environments, when this is not desired. I understand that this is correct (and essential) CVS behavior, but is there anyway around this? Or is there another way to implement what I am trying to achieve. I have read the branches should be used for releases, but this still leaves me with the problem of not being able to selectively exclude files from the “Testing” and “Release” environments.

Any help would be greatly appreciated.

Yours truly,


reply via email to

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