Most customers are installing FlexDeploy in Test and Production environments. The purpose of the Test environment is to try various patches or beta capabilities of plugins, or even trying some complex workflows and/or custom plugins. The FlexDeploy test environment may be restricted for use to by select members of the team. It is good idea to periodically (mostly when applying major FlexDeploy upgrade/patch) clone FlexDeploy Production configuration/execution data to FlexDeploy Test environment, which will allow you to easily validate new FlexDeploy upgrades or patches.
These steps are provided as guidelines and extreme care must be taken to not disrupt your production environments.
| Info |
|---|
This process should only be followed to perform a clone of FlexDeploy Production FlexDeploy to the Test environment. Make sure that Test environment is restricted for use by very few members of your team to avoid confusion, as the purpose of the Test environment is only for validating FlexDeploy itself and is not used for actual build/deploy activities. You will do some build/deploy activities, but strictly for validation purposes. This process only applies to the 4.0, 4.0.x version of FlexDeploy. Source and target version of FlexDeploy must be same. |
...
- At this point, the Test FlexDeploy database should be copy of Production database.
- Now make various updates to make sure to limit access to the FlexDeploy Test environment and limit what FlexDeploy Test can do against various endpoints. You can customize any of these steps as per your needs. Make sure to run this on Test environment only.
Disable external realm and users, so access to FlexDeploy is very limited. Update SQL as appropriate for your setup. For example,
Code Block update fd.fd_realm set is_active='N'; update fd.fd_user set is_active='N' where local_user='N'; -- update as appropriate commit;
Disable all endpoints, so Test FlexDeploy can not run any executions until Administrator explicitly enables some endpoints. Update base directory to not conflict in case when one of these Endpoints is enabled in Test FlexDeploy. For example,
Code Block update fd.endpoint set is_active='N' where connection_type='SSH'; update fd.endpoint set base_directory = base_directory || 'fdtest'; commit;
Disable all Continuous Integration triggers.
Code Block delete from fd.project_trigger_config; delete from fd.project_trigger; commit;
Disable production environment. so Test FlexDeploy can not run any executions even for testing against Production environment. For example,
Code Block update fd.environment set is_active='N' where environment_code='PROD'; -- update as appropriate commit;
- Copy artifacts zip file to Test FlexDeploy server and extract it in the artifact repository folder. Make sure to run this on Test environment only.
- cd /flexdeploy/artifacts
- tar -czvf /app/backup/flexdeploy_artifacts_test.tar.gz *
- rm -rf *
- tar -xzvf /app/backup/flexdeploy_artifacts_prod.tar.gz
- Now FlexDeploy artifact repository is also copied.
- Now you can start Test FlexDeploy and validate it.
- You can make necessary adjustments to Realm, User, Groups to validate setup and perform tests as necessary. This is necessary as we disabled user and realms in previous steps.
If you have workflows that perform tags on Source Control Systems, make sure to update the workflows before running builds, so you do not conflict with tags created by Production FlexDeploy. You can do this by simply running this SQL also. Adjust according to your requirements.
Code Block update fd.project_stream set version_syntax = ' + ".fdtest"' || version_syntax; commit;
- Update System Settings.
- Change FD_SERVER_BASE_URL.
- Change SMTP_FROM_ADDRESS. This will make sure that emails are coming from different address for Test FlexDeploy.