Deploy a Release
Last updated
Last updated
Deploying a Release is currently a standardised process that is part of the .
To trigger the Default Deployment Pipeline for a Deployment:
Go to Modules -> Environments
Select the desired Module from the list
Use the Config popover to specify settings for the Deployment Pipeline
Use the Deploy or Roll Back popover to trigger the Default Deployment Pipeline now, or schedule it for later.
Monitor the status of each step in the pipeline from the Migrations view
| Name | |
|---|---|
| Name | Description |
|---|---|
| Name | Description |
|---|---|
| Name | Description |
|---|---|
Account
Account name for the Deployment, if different from the Module.
Password
Password for the Deployment, if different from the Module.
Encryption Key
Encryption key for the Deployment, if different from the Module.
Ignore Value Lists
Uses custom value lists from the released Version instead of the Deployment.
Ignore Accounts
Uses the account names, passwords, and the encryption password from the released Version instead of the Deployment.
Ignore Fonts
Doesn't check the font mapping for field contents.
Rebuild Indexes
Rebuilds existing indexes during migration instead of copying them from the Deployment.
Reevaluate Stored Calculations
Causes all stored calculations to be reevaluated.
Note: Calculated values are recomputed and the orginal values might change, especially if the calculation includes some of the Get functions, the Random function, or any external functions (because the data migration tool doesn’t load any plug-ins)
Timeout
A timeout (in minutes) for the Data Migration process on the target server. Defaults to the Project's Default Migration Timeout (600 mins).
Name
Name of the script to be run after the data migration (beware of script name limitations in the FM OData API)
Parameter
Script parameter for the script
Type
Parameter type
main to the PROD environment