...
FlexDeploy is installed on each isolated network, and plugins are also installed as part of installation.
All FlexDeploy installations participating in isolated network architecture must be at same version. At times, even minor releases also introduce database changes, so strict version match is required.
Source server is where builds will be executed. There will be only one such source server.
Target server is where builds will be imported and deployments will be executed. There can be one or more such target server.
Environments, InstancesTarget Groups, Projects etc. will be configured on Source server. Configuration export will be done for import to Target server.
...
Make sure to configure Source environment for Projects, EnvironmentEnvironments, Instances Target Groups etc.
Perform configuration export and import from Source to Target as and when necessary. This export can be done by using Administration - Admin Operations option.
Builds can be exported individually from workflow execution page or as a group from Snapshot 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 as 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.
...
The folder contains the configuration for the whole server including the topology (environments, target groups, plugins), workflows, and projects. Please see the Properties Not Exported section for items that are not included with exports. Once the configurationis exported successfully, it can then be imported to an Isolated Network Target Server. See Isolated Networks Import Documentation.
Export Snapshots
Snapshots can be exported from any release assuming that they were initiated successfully. To do this, go to the Releases screen and click on the name of a release.
...
The exported snapshot will contain all of the server’s configuration at the time of the release, as well as any build executions associated with the projects in the release. Please see the Properties Not Exported section for items that are not included with exports. Once the snapshot is exported successfully, it can then be imported to an Isolated Network Target Server. See Isolated Networks Import Documentation.
Export Builds
Build workflow executions can be exported from any project assuming that they completed successfully. To do this, go to the executions tab of a project and click on the id of a successful build.
...
The exported build will contain all related data as well as the package data associated with the execution. Please see the Properties Not Exported section for items that are not included with exports. Once the build is exported successfully, it can then be imported to an Isolated Network Target Server. See Isolated Networks Import Documentation.
| Note |
|---|
Note that the project configuration must also exist on the target server in order for the import to be successful. See Export Configurations |
...
Snapshots will not import if there isn’t a pipeline associated with the release on the target server. To solve this problem, go to the releases page and click on the release’s id. Add a pipeline and start the release. Then the snapshot will finish importing automatically. For more information on associating a pipeline with a release, see the pipeline and release documentation.