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

Question

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?

Tasadduq Burney · Answer

Answer
Bamboo should preserve the protocol embedded in an existing Git repository URL after upgrading to 7.6. An ssh:// URL or git@host:path.git SCP-style URL remains SSH; an https:// URL remains HTTPS. Bamboo does not appear to rewrite an existing URL scheme merely because no protocol preference is specified.
Two caveats: I have no verified Bamboo 7.6 release-note evidence that unspecified protocols now resolve to HTTPS instead of SSH, so treat that reported default change as unconfirmed. I also know of no standard plan-level or agent-level setting that forces SSH as the default protocol. Enforce SSH by using an SSH repository URL with an SSH-key credential.
Confirmed behavior versus unverified claims

StatementStatus

Repository URL scheme determines Git protocolConfirmed
ssh:// and git@host:path.git use SSHConfirmed
https:// uses HTTPSConfirmed
Upgrade rewrites SSH URLs to HTTPSUnverified; no release-note evidence
Agent or plan option to force SSH defaultNone known

Verification steps

Open Plan configuration > Repository and read the Git repository URL. ssh:// or git@host: indicates SSH; https:// indicates HTTPS.
Compare the current URL against a pre-upgrade plan backup or Bamboo Specs export. Check for URL, credential, or SSH-key changes.
Inspect the credential store entry used by the repository. SSH-key credentials support SSH; passwords or tokens suggest HTTPS, though the URL scheme is authoritative.
Run a read-only reachability check on the agent without starting a build:

git ls-remote ssh://[contact removed]/PROJECT/repo.git HEAD
Do not embed credentials in the command, and do not rewrite SSH URLs to HTTPS based on the unverified claim.
Missing diagnostic detail
Confirm whether Git runs from the plan repository field or from an inline script/task. Inline scripts can use their own URL and credentials, which the plan repository UI will not reveal. Also confirm the exact Bamboo patch version, since behavior may differ across 7.6.x releases. This detail determines whether UI inspection alone is sufficient.

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

1 answer

Answer

Confirmed behavior versus unverified claims

Verification steps

Missing diagnostic detail

Your perspective belongs here.

0 question comments

Statement	Status
Repository URL scheme determines Git protocol	Confirmed
ssh:// and git@host:path.git use SSH	Confirmed
https:// uses HTTPS	Confirmed
Upgrade rewrites SSH URLs to HTTPS	Unverified; no release-note evidence
Agent or plan option to force SSH default	None known