Introduction
The PVCS series software is a CASE tool for MERANT to implement configuration management that provides good automation support for configuration management.
Where PVCS Version Manager is used to implement file management, it is the core of the entire kit.
PVCS VM Server is a server that uses a web way.
PVCS Tracker is mainly used to manage defect tracking and change request management.
This article takes a small and medium-sized software development enterprise as an example, indicating some of the features of the system in deploying and installation.
the goal
u Realize configuration management in the development project. The core is the version management of the source code, documentation and other configuration management items in software development.
u Support the client to use a web browser to access the configuration management library.
u Establish defect tracking and change processing support system.
u Automatically notify the relevant personnel with the corresponding event of the configuration management.
Software Environment
1. One Windows 2000 Server server runs Microsoft Internet Information Server5.0.
2. Installing Microsoft SQL Servera or with client software to access another dedicated SQL Server database server.
3. LAN Based on the NT / 2000 domain model, there is a machine installed with Exchange Server 5.5 or 2000 as a mail server.
4. PVCS Series CD
PVCS Version Manager V6.7.10
PVCS VM Server V6.7.10
PVCS Tracker v7.0.10
PVCS Notify V7.0.10
The first part of the Version Manager build version management library
installation
In this system, version management is the core of software configuration management. So you need to install version management software first.
After inserting the PVCS Series CD, run
: / VM / Win32
SETUP.EXE, follow the prompts to select the installation step by step.
figure 1
Version Manager contains the following components:
GRAPHICAL User Interface
GUI. The user can perform relevant operations via it.
2. Project Command-Line Interface
Project command line interface (PCLI). The command line is used to manipulate the item library and complete some operations, mainly for the convenience of the script to complete some automatic work.
3. Command-line Interface
Command line interface. Includes some commands used to complete the version management work.
4. VM I-NET INTERFACE
Web-based interface. When using the VM Server, you can complete the version management work through it.
5. VM Development Interface
Development interface. Interfaces integrated with some mainstream development tools such as VC, VB, PowerBuilder, Rose, etc.
6. PVCS Developer's Toolkit
Provides an application programming interface that is developed with VM integration.
Create project library
After the Version Manager software is installed, the project library needs to be established for the development of software items. Considering the need to install VM Server later, it is best to leave an empty logical disk on the server to be used as a dedicated disk of the project library data storage.
Use NT / 2000 disk management tool to change its disk to a larger, generally rarely use the disk number like t, name the T disk's volume label is pvcsdata (or you like), then The entire disk is shared, don't start a shared name PVCSData.
Open the PVCS Version Manager tool in the Start menu, and an SAMPLE library is installed by default, shut down the Sample library. Select Create Project Database under the admin list to create a project library. Enter the name of the project, the location of the project library (typically located in a directory under the data disc), and does not modify the position of the archive file. Enter the position of the work file, the general working file path refers to the storage location of the file coming out. It should be noted that the location of the working files specified here is for the root workspace, and all users can work, if the client needs to specify a different working file location, you can set the private workspace.
figure 2
Configuration permission
After creating a project library, you need to change the permissions settings for the project library.
By default, the item library does not set an access control library (Access Control Database), you need to set in Admin -> Configure Project ....
On the General page of the following Configure Project Database dialog box, select Access Control Database under Security, if you are a new project library, you don't have to change the other, just hook your hook in front of Enable Access Control Database Security, open access control Library switch.
image 3
Then select the Login Source under Security, Version Manager has a variety of ways to provide the username. If your client's machine name is consistent with his username, you can use the Host ID method, if it is a Windows user name, choose WNET ID, if the user needs to provide a username each time you log in, you can use the login Dialog mode, you can also combine but row priority.
In Source Detail, normally, when the current username is supplied, whether the user name is automatically created in the access control library, and the new user has permissions in the default case. Here is the first username to provide a new username, the new user's permissions are documentation, and the specific permissions can be viewed to Admin-> Security -> Privilege Sets.
Figure 4
Create Workspace
Workspace In PVCS Version Manager refers to a collection of settings for some of the contents of the project, there are public and private points, and public Workspace works to select its users, while private can only affect users with it.
Multiple Workspace, such as DEV, TEST, DOC, etc. for different roles, such as DEV, TEST, DOC, etc. You can create from private Workspace, if the user does not change the settings, inherits its previous Workspace.
Figure 5
Client installation and configuration
Close the Sample project.
The project data shared by the server is mapped to T (consistent with the data drive of the aforementioned server).
Use PVCS Version Manager to open the item database located on the T disk.
If some of its own settings are inconsistent with public settings, if the position setting of the work file is inconsistent, it is necessary to create a private Workspace. After selecting private Workspace, the Workspace name next to the user name in the PVCS Version Manager status bar is changed to the selected Workspace, right-click the item database, select SET WORKFILE LOCATION to select the location where you have your own work file.
Join work file
After configuring the server and client, you can join the file (source code, document, etc.) that you need to manage (source code, document, etc.) into the project library. First, organize the file directory of the project, and copy it along with the directory structure to the set work file location.
Right-click Project Database, choose Add Workfiles ...
In the Add Workfile dialog, confirm that the path listed in the Add Workfile from column is the path where the workfinder is located. Hook hooked before INCLUDE Workfiles in subdirectories.
Enter some descriptions.
Top the hook in front of the Use Description for ALL.
Select Delete Workfile to delete a work file after check in, which file can be seen which files have been added yet.
Image 6
OK, now the file that needs to be managed is added to the project database.
Figure 7
