...

• FlexDeploy is installed on each isolated environment, and plugins are also installed as part of installation.

• All FlexDeploy installations participating in isolated network architecture must be at the same version. At times, even minor releases also introduce database changes, so strict version match is required.

• There will be only one such source server, but there can be one or more such target server.

• Builds are executed on source server and are imported to target server(s). Builds can not be performed on target server.

• Environments, Target Groups, Projects etc. will be configured on the source server. Configuration export will be done for import to target server.

• Topology

  • Target Groups and Environments must be configured on the source server and imported to any target servers.

  • Environments and Property Sets must also be assigned to Target Groups on the source server and imported to target server.

  • Endpoints can be created and assigned to Targets on the target server. Also, property values can be edited for Targets on the target server.

• Projects

  • Projects can not be created or configured on the target server. Projects can only run builds on the source server, which can then be imported to the target server where they can be deployed and tested.

  • Folder and Project issue tracking configurations should also be managed on source server and imported on to target server.

  • Project and folder security is managed separately on source and target servers.

• Release

  • Releases and Snapshots can be created on the target server. However, since build can not be performed on Projects on the target server, these can only be created with existing project versions.

• Pipeline

  • Pipeline must be created on target server as it will handle deployments to different endpoints than source server. Note that source server may be deploying to zero or more environments depending on isolation requirements.

• Integrations

  • Integration Providers can not be created on the target server and will be imported from the source server. Integration Instances can be created on the target server.

• Security

  • All users, groups, and permissions are managed separately on source and target servers.

• Workflows cannot be configured on target server, hence must be imported from source server.

...

Once the configurationis exported successfully, it can then be imported to an Isolated Network Target Server.

Configuration Export Content

• All Workflows (Internal and Read-only workflows are excluded).

  • Only active version.

  • Workflow Properties (Property Set).

• Topology

  • All Environments and Target Groups.

  • Target Group mappings with Environment and Workflow / Plugin Operations. Note that Target Endpoint and Property Value configurations are not exported.

  • Custom issue tracking systems including their Properties.

  • SCM and Issue Tracking integration instances with Property Values.

• All Folders

  • Folder level Release Settings.

  • Folder level issue tracking configurations are not exported.

• All Projects

  • including sources, branches, workflow and target group configurations.

  • Project File Catalog.

  • Project Property Values.

  • Test, Replacement and Issue Tracking Configurations.

Export Snapshots

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.

...

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 content project and release level settings (if overridden)

• 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 Release

  • including sources, branches, workflow and target group configurations.

  • Project File Catalog.

  • Project Property Values.

  • Test, Replacement and Issue Tracking Configurations.

Export Builds

Build workflow executions can be exported from any project assuming that they completed successfully. To do this, go to the Execution tab of a project and click on the id of a successful build.

...

Build Export Content

• Only successful builds can be exported.

• Build execution and project version (including package) details

• Build Artifacts

• Associated Work Items and Commits

• Scan and Test results

• Build Request details including Inputs

Import on Target Server

First make sure you are connected to a target server. Then you must take an export and put it inside of your fdexports folder. This may be <flexdeploy_home>/application/fdexports depending on how FlexDeploy was installed. To do this, you may use any file transfer tool or method available and approved by your network and security teams.

...