How to prevent test server from changing production

[Mark Wolff]

We have a clone of the production system that we use to test upgrades and the like, as is suggested by the documentation.  The issue is that whatever we do to the clone, happens to the production.  We even went into the "General Configuration" page and change the server's address and it changes both systems.  We do not have and do not want clustering in this case.  What are we doing wrong?

[Shashank Kumar]

Hello Mark,

Welcome to Atlassian community.

Can you be little bit more clear with the below, what things are getting updated

The issue is that whatever we do to the clone, happens to the production.  We even went into the "General Configuration" page and change the server's address and it changes both system

I presume your database in bamboo.cfg.xml is pointing differently in both and test environment.

There are few important configurations which you need to make sure are right in the test environment

1. The new home directory: Make sure that the new Bamboo server points to the new home directory. The configuration file is <bamboo-install>/atlassian-bamboo/WEB-INF/classes/bamboo-init.properties

2. Base URL: Make sure to change the baseurl configuration to the new one from <bamboo-home>/shared/configuration/administration.xml

3. Database connection: Make sure to change the database connection to the new one from <bamboo-home>/bamboo.cfg.xml

4. Change/Remove application links to the production environment

5. You can also refer the page https://support.atlassian.com/bamboo/kb/how-to-start-up-bamboo-with-build-plans-deployment-environments-branch-detection-and-build-status-updates-disabled/ to see how to disable auto builds and change detection which can be done on the test environment

Regards,

Shashank Kumar

**please don't forget to Accept the answer if your query was answered**