Bamboo 7.6 Git Integration Defaults to HTTPS Over SSH for Unspecified Protocols

This review covers plan configurations after upgrading to Bamboo 7.6 or later. The goal is to determine whether existing Git repository tasks that omit an explicit protocol now resolve to HTTPS instead of SSH, and whether this affects plans previously dependent on SSH-only repository access.

Bamboo's global credential store supplies credentials at plan start, and agents cache them for the build duration. Because the default protocol preference changed, URL handling may differ between newly created tasks and legacy tasks migrated from earlier versions. It is unclear whether an existing SSH URL continues to use SSH or whether Bamboo rewrites it to HTTPS when no protocol is specified.

Does Bamboo preserve the protocol embedded in an existing Git repository URL after the upgrade? Is there a configuration option to force SSH as the default protocol at the agent or plan level? How can administrators verify which protocol a specific Git task uses without triggering a build?