...

FLEXAGON_FD_JAVA_ARGS="-Dflexagon.fd.isolatednw.targetserver=true"

Execution

• Make sure to configure source environment for Projects, Environments, Target Groups etc. Additionally, map Environments with Target Groups, making sure to include isolated environments.

• Perform configuration export from source server and import onto target as and when necessary. This export can be done from Administration - Admin Operations page.

• Builds can be exported individually from each workflow execution page or as a group from Release Snapshots page.

• All export files (configuration, build, snapshot etc.) should be placed in fdexports sub-folder on server working directory on target server. Files will be automatically imported and deleted on successful import.

• If you are working with snapshot export and the release does not yet exist on the target server, then the release will be created with the status set to Not Started. This means that snapshot is only partially imported. You must associate a pipeline to that release and then start it. Snapshot import will complete after that automatically.

...

If FlexDeploy is running, it will automatically start the import process shortly and delete the zip file from your fdexports folder once import is completed. This may take a few minutes to get started. This same process can be done with exported builds, snapshots, or configurations. It can also do multiple different export types at once, but it may take a bit longer. Snapshots and configurations will work on an empty or full server, but an exported build may need configurations or snapshots to be imported first, as it needs an associated project to import into. Snapshots and configurations may take a long time to import

Snapshots and configurations import may take a longer, but builds should be imported fairly quick.

Configurations can be imported many times as configurations change on source server. Import process will handle the import with necessary create, update, delete.

...

...