Managing packages

Packages represent a snapshot of an application design and allow properties to be parameterized within the design. We can also say that the package represents a particular build of an application.

A package is the smallest unit that can be deployed for an application. It represents both the implementation artifacts (the manner in which an application should be deployed) and deployment artifacts(the location of libraries like war, ear, etc., that should be deployed).

Packages are associated with a lifecycle stage. A package can belong to Development, Testing, Staging, or Production stages.

Packages are associated with pipeline management. They can be managed across lifecycle stages, such as promotion or rejection in a given stage. For example, a user with the QA role can reject a package. See Lifecycle stages and actions.

Tasks

• Create a package from a specific application version. An application version can consist of multiple packages. See Create a package.
• Deploy or redeploy a package. In this case the corresponding state of an application design along with the properties of the design specified in the package will be fulfilled. See Deploy a package.

• Delete a package. Go to the Release Pipeline tab, press and hold down Ctrl to select multiple packages, and click Delete.

  To delete a package

  1. Click Release Automation >> Release Pipeline.
  2. From the drop-down list on the left side of the screen, select the type of application design from which you need to delete a package (Topology Designs is selected by default).
  3. Click the application design version, which contains the package you need to delete. All packages pertaining to their respective lifecycle stage for the selected application design version are displayed.
  4. Click the package you need to delete.
  5. Click the gear icon pertaining to the package you want to delete and select Delete.
  6. In the Confirmation Required dialog, click Yes to confirm package deletion.

  Note You cannot delete a package if: 

  • it has an action instance associated with it.
  • it is in the last stage of the lifecycle. Such a package must first be rejected before it can be deleted.