...
For more information on utilizing Isolated Networks see here.
...
Note that very strict security restrictions in such configurations require manual copies of files, this is mainly driven by security practices of specific organizations.
Export from Source Server
FlexDeploy allows Configurations, Builds, and Snapshots to be exported. For these options to be enabled, FlexDeploy must be configured as an Isolated Network Source Server. See the Configuration section above.
...
FlexDeploy configurations can be exported which includes the environments, target groups, workflows, and projects of the server. The user must have administrator privileges to download the server configuration. To do this, go to the Administration → Admin Operations screen and change the operation name to Export Configurations, then click the Export button that appears.
...
| Info |
|---|
The configuration export may take some time depending on the amount of data on the server. |
...
Once the configurationis exported successfully, it can then be imported to an Isolated Network Target Server.
Configuration Export Content
...
Snapshots can be exported from any release assuming that they were 
Initiated. To do this, navigate to the Releases screen and click on a release from the folder content.
...
From here, go to the Execution tab, click on the actions menu of a snapshot that was Initiated, and then click Download Archive
...
| Info |
|---|
The snapshot export may take some time depending on the amount of data on the server. |
...
Once the snapshot is exported successfully, it can then be imported to an Isolated Network Target Server.
Snapshot Export Content
Only Successfully built snapshots can be exported.
Release definition including project content.
Snapshot versions including workflow execution details for each project version
Build execution and project version (including package) details
Build Artifacts
Associated Work Items and Commits
Scan and Test results
Build Request details including Inputs
Project details of all projects in the Release
including sources, branches, workflow, and target group configurations.
Project File Catalog.
Project Property Values.
Test, Replacement, and Issue Tracking Configurations.
...
The exported build will contain all related execution data, artifacts, and package data associated with the execution. Once the build is exported successfully, it can then be imported to an Isolated Network Target Server.
| Note |
|---|
Note that the project configuration must also exist on the target server for the import to be successful. See Export Configurations. |
Build Export Content
Only successful builds can be exported.
Build execution and project version (including package) details. The package will be Activated on import if it was previously completed.
Build Artifacts
Associated Work Items and Commits
Scan and Test results
Build Request details including Inputs
...