Create a development package
A development package is very similar to a release package (created from the main dashboard) with a few differences:
Can contain experimental CMS/XFP versions. From time-to-time, we may offer a pre-release version of a product to be patched via Deployer, which we call "experimental" versions. This is typically where significant changes have been made to the product(s) which may impact custom developments you have, so we provide a pre-release version to give you a bit of extra time to assess and make any required changes before that version of the product is officially released.Experimental product versions SHOULD NOT be deployed to production environments.
Can be built from any branch with the exception of main branches (
dev,develop,master,hotfixlive) and will contain any code that is on that branch combined with a CMS/XFP version (if combined package is selected)
The main purpose for a development package is to test new and experimental CMS/XFP versions as well as test new custom features on development environments, while keeping the main branches and primary environments (LIVE/UAT) untouched.
In order to use development packages, your project needs to use deployer-integration version 1.6.0 or higher. If you don't know which version your project is using, please contact Jadu Support.
Creating a development package can be achieved in two ways:
Choose No (default) for Combine with product if there are only front end (client) changes in this package and CMS/XFP versions remain the same. This option will create a client only package
Choose Yes for Combine with product if the new package will contain a new CMS or XFP version. This option will create a combined project package. Before creating a package you can also specify a new CMS or XFP version. If you don't specify a new version, the package will contain the same version as what the branch dependencies specify. If the project you are working on also has XFP, then you can only choose an XFP version and the CMS version will be preselected. For development packages you can also choose experimental versions of CMS or XFP.
Branch name from where the package should be created from. The branch name should come from your project repository and should be present before creating a development package. The branch name needs to match exactly the name in the repository and it is case sensitive. If the package is created with a combined CMS or XFP version then the dependencies are pushed into this branch.
After configuring the package, click Create package. This will start the packaging process and usually takes around 10-15 minutes.
You can view the progress of your package request in Package Request History