A deployment package can be deployed on the Cloud Portal or on a server that is configured to run Mendix software. While developing you can deploy and run on your local machine, but once you are ready to deploy your project on a real server you will need to create a deployment package.

Versioned

A versioned deployment package is built from a fresh download of a specific revision in the Team Server. This means that you can always trace its origin and recreate it. An unversioned deployment package is based on your local project on disk and cannot be traced back to a specific revision. Therefore, we recommend that you create versioned deployment packages unless you have very good reasons.

Development line (for ‘Versioned’)

Choose the development line for which you want to create a deployment package. This can be the main line or any branch line. For example, you create a package from a maintenance branch line if your want to put a fix you implemented there online. Or you create a deployment package from the main line because you are ready to deploy the next big version of your application.

Revision (for ‘Versioned’)

Choose the revision of the selected development line for which you want to create a deployment package. This is not necessarily the latest revision because you might want to exclude some recently developed functionality.

New version (for ‘Versioned’)

Choose a version for the deployment package. The version consists of four numbers: major version, minor version, patch and revision. The revision is fixed and determined by the revision you selected for ‘Revision’.

The other numbers are free to choose but it is wise to use a convention for the numbering. Major versions typically contain major new feature or rewrites of existing features. A minor version contains small new features and fixes. A patch solves minor issues and should not change the data model of the application. A patch release should be interchangeable with another patch release with no changes to the data.

The Modeler will show you the latest version that you created a package for (if any). You can increase major, minor or patch according to the convention you use.

Description (for ‘Versioned’)

You can enter a custom description for this deployment package. It is purely for your own reference so that you can quickly recognize a package. The Cloud Portal will show you this description along with the version number.

Disk location

The location where the deployment package will be placed is shown here. This is not editable. All packages are placed in a directory ‘releases’ inside your project directory. This directory is automatically ignored so that these packages will not be committed to the repository. You can always recreate a deployment package (assuming you have the Modeler version you used) so there is no need to put them on the Team Server.