...
| Tip |
|---|
Test automation, triggers, and tags will not be included with project exports and they cannot be reconfigured on the target server. Test and scan results will be exported if they are associated with a build execution, meaning test, utility, and deploy executions will not be exported. Additionally, credentials are not exported, meaning all cloud accounts and source control management passwords associated with a project will have to be reconfigured on the target server. Project packages and artifacts will only be exported with a build containing the package (see Export Builds) or with a snapshot of a release containing the project and its packages. |
...
| Note |
|---|
Note that the project configuration must also exist on the target server in order for the import to be successful. See Export Configurations. |
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.
...
Snapshots and configurations import may take a longer, but builds should be imported fairly quick.
...
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 release. In the top left below the releases name, hover over the pipeline symbol and click on the edit pencil, lastly select a pipeline and start click the releasecheckbox to save. Then the snapshot will finish importing automatically. For more information on associating a pipeline with a release, see the pipeline and release documentation.
...
Topology: Target Groups and Environments must be configured on the source server and imported to any target servers. Environments , Workflows, and Property Sets must also be assigned to Target Groups on the source server. Environments can not be mapped or unmapped from Target Groups on the target server. Workflows cannot be configured on target server either. 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. The only editing that can be done to Projects on the target server is adding group permissions on a project or folder.
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.
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 between source and target servers.