Skip to main content
System StatusContact Support

Documentation related to the following products will soon be moved to a new portal: ( Agility, Agility Connect and Agility Integrations Continuum and ALM Connect
Links from the site will automatically redirect to the new site.
If you have any questions, please contact Support. Agility Community

Packages and Revisions

What is a Package?

A package in Continuum is a trackable version of one or more deployable objects, aka artifacts. Each time one of the artifacts is built, or revised a new revision of the package can be revised as well. Changes and workitems are associated with the revision and between one revision and another a delta of changes and workitems can be determined. All of the important Continuum delivery metrics are pacakge based.

FAQ: What is the difference between an artifact and package? A package can represent more than one artifact and can span more than one project or repository.

Create a Package and Associate the Artifact

In the Continuum UI, navigate to Flow, Manage Packages. Click Add New and name your new Package. In this most simple case, one package for one project, you can name the package the same as your project or repository. Once it is created, click Add Artifact on the Details tab. Select your artifact that you have previously defined.

Revise the Package in the Pipeline

Return to the Pipeline Definition editor. Add another step below the step to revise the Artifact from the left, "Flow - Package - New Revision". The following properties are available:

Package Name: Required, the name of the package that was created previously. Version: Optional, the major release or version of the software package. Full Version: Optional, this is usually a release number plus a build number. Essentially a human distinquishable unique identifier for the Package Revision. Globals Key: Optional, a key in the workspace from which to pull properties and store them with the package revision. Can be used to drive automation or decisions downstream. Result Key: Optional, the results of the package revision process will be stored under this key in the workspace. Useful for reusing the package revision number in latter steps of the pipeline.

In this tutorial we will want to fill in the package name, version and full version. For the pacakge name use the package name previously created. For version for the time being put 1.0 (usually this version is derived from a build or source code file) and in full version enter the following.


Usually the full version will be related to the build but for simplicity sakes we will use the pipeline instance number.

Run the Pipeline

Make another commit and push. When the Pipeline Instance completes choose from the top menu "perspectives, packages". Select your package and click the Revisions tab. You should see a new revision, the number of Changes and Workitems associated with it, etc. As you continue to make changes and further pipelines run, you will see this list grow. Clicking on a row will allow you to see the difference between one package revision and another within the same version.


After you have completed the instructions, continue with the next step Deployments