Packages in CA Harvest SCM describe how files are added or modified. Packages also move changes from one state in the lifecycle to another state.
You can add as many packages as you want in the lifecycle in your project. However, if you do not have at least one package defined initially, you cannot check out any files for update or check in files to your project. (Although it is possible to open a solution from the CA Harvest SCM the repository in read-only (Browse) mode.) Additionally, users should create their own individual packages for adding or modifying project files in CA Harvest SCM. We recommend that multiple users do not use the same package.
Not all functionalities that you can execute on a package are available from the plug-in. Processes such as cross project merge, switch package, delete version, move package, take snapshot view, and so on, cannot be executed from the plug-in. However, you can use the CA Harvest SCM Workbench to access all CA Harvest SCM user functions.
The Harvest SCM Explorer tree and lists view lets you execute processes and actions on packages. The following processes are available from a package node:
The following actions are available from a package node:
Renames a package.
Displays the following properties of the selected package:
Specifies the name for the package.
Specifies the Package Assignee name.
Specifies the package groups to be associated with the package. Use the add/remove buttons to add/remove package groups.
Specifies package description.
Provides notes about the create package process.
Provides approval history of the current package to discover who approved a package and when it was approved.
Provides the history of a package to discover who created, promoted, or demoted a package and when the actions occurred.
You can select multiple packages from the Lists view of the Harvest SCM Explorer and perform these operations on them.
Note: For information about setting access, see the Administrator Guide.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|