SCM-level objects are global, meaning that they are available to your entire CA Harvest SCM installation.
Note: Forms are global objects; however, forms must always be associated with a package.
The following objects are SCM-level objects:
project
A project refers to the entire management framework in CA Harvest SCM that supports a particular development or maintenance activity. You can have many different projects, depending on the applications being controlled and the kind of development activity. A project includes information about how changes progress through the development life cycle, the activities that can occur, what data to access, and user responsibilities.
Note: In previous releases of CA Harvest SCM, the term environment was used for project; these terms are synonymous.
Because the following objects are highest-level objects, you can use them in one or more projects defined in a CA Harvest SCM installation:
user and user group
A user is an individual that is defined in CA Harvest SCM. A user group is an association of one or more users. A user can belong to several user groups, and the groups imply no hierarchy. For example, a user in the Development Manager group does not necessarily belong to the Developer group. Two predefined user groups, Public and Administrator, are provided in CA Harvest SCM.
repository
A repository is a collection of items and item paths. When CA Harvest SCM is first installed, no repositories exist in the installation. Administrators create repositories and control access to them.
item path
An item path is the object that is created when a directory (or Windows folder) is first loaded or checked into a CA Harvest SCM repository. Subsequent changes to the item path (rename, move, or remove) will result in new versions of the item path.
item
An item is the object that is created when a file is first loaded or checked in to a CA Harvest SCM repository. Subsequent changes to the item will result in new versions of the item. Repositories are composed of items.
form
CA Harvest SCM forms record, organize, and track information. Forms are always associated with packages. This association helps you track problems or issues and changes you made to address them. The information recorded in a form is directly accessible from the associated package.
|
Copyright © 2013 CA.
All rights reserved.
|
|