...

• FlexDeploy is installed on each isolated environment, and plugins are also installed as part of the 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 a strict version match is required.

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

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

• Environments, Target Groups, Projects, etc. will be configured on the source server. Configuration export will be done for import to the 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 the 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 the source server and imported on the target server.

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

  • Folder settings are managed only on the source server and imported to any 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.

  • Release-level Settings and Security can be managed on target servers.

• Pipeline

  • A pipeline must be created on the target server as it will handle deployments to different endpoints than the source server. Note that the 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 the target server, hence must be imported from the source server. Workflow-level security is not allowed on target servers, must use global permissions for workflow security.

Configuration

The following assumes that you have upgraded to use setenvoverride.sh (or setenvoverride.bat) files. If you are still using setenv.sh, then changes will be slightly different. Configurations shown below must be performed in addition to following the installation document or automated installation process.

...

• Only Successfully built snapshots can be exported.

• Release definition including content project and release level settings (if overridden)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.

...