To access the Deploy page, in the left sidebar of the Release tab, click Deploy.
The following deployment methods are available:
Ad-hoc deployments mean querying metadata and/or data from the selected source and deploying the latest values into the destination.
A bundle is a pre-defined package of metadata and/or data. The data is stored as it was when the Bundle was created. When deploying a Bundle, you’ll see a preview of the contents of the Bundle, and the action that will attempt to be performed (Will Deploy or Will Delete). For more information on how to set up and use Bundles, see **Bundles.**
When deploying a Bundle as a Template, Prodly will take the Ids of all records and components from your Bundle, and use them to query the metadata or data in your source to deploy the latest values.
When deploying a Release, you’ll see a preview of the contents of the Release’s Bundles. All configuration of the deployment will be taken from the Release itself. For more information on how to set up and use Releases, see Releases.
If you have version control set up, this option will become available in Deploy. The source and destination list will be restricted to branches only, and you’ll be prompted to enter a Pull Request name and to link work item. For more information, see Pull Requests.
Deployment Method | Ad-hoc Data | Ad-hoc Metadata | Bundles including Data | Bundles including Metadata | Bundles as Templates including Metadata | Releases | Creating Pull Requests |
---|---|---|---|---|---|---|---|
Deploy to up to 5 destinations | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ | ❌ |
Select the same source and destination | ✅ | ❌ | - | - | ✅ | - | ❌ |
Validate | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ |
Temporarily deactivate events | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ |
Stopping a deployment | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
Redeploy | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ |
Select the source and destination environments for your deployment. If you're deploying a Bundle or a Release, these act as the source, so you won’t need to select a source environment manually.