We're currently in the process of upgrading our build and deployment
process for our Java environment, part of that means upgrading our
source control. Currently there is no build process in place and there
is one monolithic exploded deployment that actually has about 10-15
different applications all using the same context root. (This is a
mixture of JSP applications and Struts applications) Currently we're
using a program called AccuRev for version control. When you promote a
file in AccuRev it goes to the DEV depot. (repository) Once it's there
someone can review the files and decide to push them to the server.
After they're tested the files are pushed to the next depot for QA and
so on. The pushing of files from one repository is a manual process but
it allows the person responsible for deployment to pick and choose what
files for which applications get pushed. Since everything is deployed
as one application this works out good if we have people working on
different applications at the same time. Starting with this upgrade all
new projects will be developed outside of the old application as
individual projects. We still need to maintain those old applications
until we separate them out into new applications or they reach their end
of life. I'd like to get rid of AccuRev and replace it with SVN but not
sure how we can use SVN to decide which files need to go in the build
and which don't.
Example:
Dev A is working on App 1 and commits files to SVN
Dev B & C are working on App 2 and commits files to SVN so they share
their work.
These are all in the same repository...how can I set this up so a build
script (Ant) will know which files to take the head version of and which
ones to get the previous revision (committed?) of?
Thanks,
-Jeff
NOTICE - This message and any attached files may contain information that is confidential and/or a subject of legal privilege meant only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient be advised that you have received this message in error and that any dissemination, copying or use of this message or attachment is strictly forbidden, as is the disclosure of the information therein. If you have received this message in error please notify the sender immediately and delete this message.
This email has been scanned by the MessageLabs Email Security System.
Received on 2008-05-07 23:11:31 CEST