You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
1. Added a Project via web UI
2. Walked through Specs > "Set Up Specs Repository" and linked the target repository.
3. Pushed a Bamboo.yaml file located in bamboo-specs directory inside the repository root.
4. Manually went to the Linked Repository settings and clicked "Scan" to scan for bamboo specs.
The prompt then said it's attempting to scan but immediately finished without finding any and said the repository was never scanned. After reading related support articles I gathered that adding a more up-to-date git capability was a common solve for this issue and we added git for windows to the Bamboo agent server. Though when we then added Git to the Server Capabilities, all Bitbucket-linked plans and repositories lost their connection. I hit "save changes" to force a retry of the remote connection and was given the error in the attached screenshot.
"Unable to negotiate with [IP] port [port]: no matching host key type found. Their offer: ssh-rsa fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists."