[Top][All Lists]

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

partitioning cvsroot into dev, qa and pdc areas..

From: Kevin Duffey
Subject: partitioning cvsroot into dev, qa and pdc areas..
Date: Mon, 18 Aug 2003 15:40:57 -0700 (PDT)

Hi there,

Been using CVS for some time via sourceforge, but now
I am instructed to figure out how to develop our
security model and such with CVS as we move our code
to CVS internally.

I did the usual:

cvs -d /usr/local/repository init

did the chgrp, chmod stuff, etc.

Now, the IT team figures we should put files below the
root starting off with project name, then below each
project section it off for qa, dev, pdc's, etc. Below
each of these groups, put all the stuff related to
each section, such as the version of the project,
shared code areas, etc. However, shared code, for
example, may be needed across projects, so it seems
unfitting to put it under each project.

My thought was the opposite. Make a /dev, /qa, /pdc,
etc below the cvs root (/usr/local/repository). Below
each of these, put the projects, shared code, etc. The
idea here is that we are using our single CVS server
for several departments, including documents,
management, product coordinators, dev, qa, and so
forth. I personally think sectioning it off into
individual departments first, then below that putting
specific department data is the way to go.

However, there is IT's take on this which is, below
/dev, /qa and /pdc, we'll have the same project names
and below those the same versions. Therefore, we are
duplicating the /department/project/version path under
each department.

Ok, so two questions to ask in regards to this. First,
the main issue I am having is that I have created
/usr/local/repository/dev/myproject. In Eclipse, my
IDE of choice, I can connect to the cvs repository no
problem. In my repository view, I can see HEAD, below
that CVSROOT, dev, qa, pdc and so forth. If I expand
the dev dir, I see myproject just fine. My problem is,
I am starting off a new project in CVS below the /dev
sub folder. I want to add in the files to CVS for the
first time. Eclipse provides a Check out as feature
that allows you to check out a project into a new
Eclipse IDE project folder and work on it from there.
However, my connection string is basically:


Below that is CVSROOT. So how do I start a project
that is at /dev/project-name in CVS that is able to be
worked against on my local machine? I can't name the
project dev/project-name. I tried adding
/usr/local/repository/dev as the cvs location, but it
says it can't find CVSROOT (as expected), so how do I
dive one sub-folder below the root location to get to
my projects? Not sure if I am asking this right, so
I'll try another way just in case, I basically need to
keep all projects for dev below a cvs root dir of
/dev. But in the IDE, the project is not named
/dev/project-name, it is just project-name. When you
try to access the cvs /dev/project-name from CVS, how
do you do this in the IDE (or for that matter, winCVS
or anything else) so that you can directly access the
project in the IDE and its commits get committed to
the /repository/dev/project-name project and not the
/repository/dev folder in cvs?

Second, does it seem logical to do it in this manner
as opposed to:


Also, in regards to this, it seems to me that setting
user/group permissions based on the
/<department>/project approach as opposed to
/project/<department> will be much better and more
controllable. I need to get confirmation on this
specific issue as well, because while both result in
the same number of files (folders, project files,
etc), adding a new QA engineer to the QA group that is
matched to the /repository/qa folder, as opposed to
having to set up the QA group to every new project
using the /repository/<department>/project/qa
approach, just seems to make more sense. I suppose
since projects aren't added all that often, and simply
adding a new engineer to QA will automatically make
her available to all projects with the QA group
matched to it is fine, it just seems to be more

Thank you very much for any help at all.

Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software

reply via email to

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