Creating a deployment package

Packages are archive files created by "zipping up"" the project folder and all of its subfolders into a single "deployable archive". How this is done will depend on the artifact plugin defined for the project.

The package created will be stored according to the location specified by the artifact plugin.

Created packages will be visible on the new job panels when performing a deployment or creating a job plan.

External resources

Created packages can additionally contain one or more external resources that are added to the package during the package creation. These resources are selected on the project main panel by selecting from the list of available resources.

New resources can be defined on the resources panel, by defining a resource based on one of the external resource types (Maven, SCP, FileSystem, HTTP (wget) etc). All defined resources can be consumed by any project.

Archive types

Packages can be created as jar, tar or zip files. Please note that tar files do not include any compression and so may be larger that the corresponding zip or jar formats.

Framework server package manager

You can create a package manually from the Web Services interface or through the UI. Packages can also be created automatically for any of the projects in a pipeline by selecting NEW_VERSION in the version selector for one of the Project/Targets in the pipeline. In this case a new package is created at the start of the pipeline and used for every target in the pipeline for this project.

In the UI you follow the process below:

  1. In the menu, go to 'Projects'.
  2. Select your project. Use either the project name link or via the pencil icon on the 'Action' column.
  3. Select the 'Packages' tab.
  4. Click the 'Create Package' button to use the one click package create feature

    This will automatically build a new deployment package with the same extension and incremented version, or in case no packages found it will create the first version of the package in jar format.

Build process

It is also possible, and sometimes desirable, to create the package as a step in the projects build or continuous integration process, invoked directly from your existing build process. This is only recommended when invoking a project/target combination directly. If invoking a pipeline, use the NEW_VERSION selector in the pipeline instead.

Visit the MidVision GitHub page to see current integrations for Jenkins, UrbanCode, Go and Bamboo, or download the generic connector jar to create your own integration.