Issue Summary

This is reproducible in Data Center:

Bamboo allows using the same location for both <bamboo-home> and <bamboo-install>. Setting the same path for both properties works but will be a huge pain when upgrading and will likely generate several issues and confuse support during any troubleshooting.

Steps to Reproduce

1. Install Bamboo on Linux or Windows
2. Set <bamboo-home> to the same location as <bamboo-install>

Expected Results

Bamboo should refuse the start if <bamboo-home>:

• Points to the same Canonical path (readlink/CanonicalPath) as <bamboo-install>
• Is contained or is part of <bamboo-install>'s canonical path (a subfolder/subdirectory)
• The Bamboo Windows installation Wizard should also consider those folder constraints
• Check on the provided <bamboo-home> for any <bamboo-install> Tomcat or jar files presence as a secondary check in case the folder validation is not accurate (NFS mounts, bind mounts, etc)

Actual Results

• Bamboo accepts any <bamboo-home> folder, even if that's the same as <bamboo-install>

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available