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, hold Ctrl to select multiple packages, and click Delete.

  You cannot delete a package that has an instance associated with it.