Using Packages › Promote a Package

Promote a Package

The promote process lets you move one or more packages in the current state to the next state in the lifecycle. If an approval process exists for a state, approvals are verified before a package can be promoted. When you promote a package to a state with another view, all its changes become visible in that view.

If a package is part of a bound package group, all packages in the group must be promoted together. To promote a single package that belongs to a bound package group, you must first unbind the package.

Follow these steps:

1. Navigate to the package you want to promote.
2. Right-click the package, and select promote process from the shortcut menu.

   The promote process dialog appears and lists the package you selected.

   Note: The lowercase italic text indicates the process dialog name by the process type, since the process execution dialog names differ to each site.

3. (Optional) Click Add (the plus [+] sign) to open the Select Packages dialog from which you can select packages in the current state. Click OK.

   The packages are added to the promotion list.

4. (Optional) Select packages from the list, and click Remove (the minus [-] sign)

   The packages are removed from the promotion list.

5. (Optional) Select options for promoting the package:

   Note: If an option is enabled by default, it is enforced and you cannot override it.

   Enforce Package Bind

   Promotes all the packages belonging to a bound package group together.

   Enforce Package Merge

   Prohibits promoting packages to the next state if the packages are associated with branch versions. If the promote process is in a state with no view, or if that state's view is the same as the one in the Promote To state, this option is not enforced.

   Verify Package Dependency

   Prohibits promoting packages that depend upon other packages. The dependency is based on versions in the view. You cannot promote a package with a higher item-version without also promoting the packages with the lower item-versions in the current view unless the lower item-versions already exist in the view of the destination state. If the promote process is in a state that shares the same view as the one in the destination state, this option is not enforced.

   Note: The lower item-version causes a dependency error only when it is on the trunk.

   Add Dependent Packages

   Allows adding dependent packages also to the list of packages being promoted. To avoid conflict, it is recommended to promote all the dependent packages together. This option retrieves details of the dependent packages and lists the details in the Dependent Packages tab. The details include the list of dependent packages, their associated versions which made them dependent, and all other versions.

6. (Optional) Select the Approve before promoting option to approve the package before promoting it.

   Note: If multiple approve processes are defined for the state, a menu appears that lets you select the approve process you want to use.

7. (Optional) Click Note to view notes about the process.
8. Click OK.

   The package is promoted and appears in the destination state.