Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,506,715
Community Members
 
Community Events
180
Community Groups

Unable to detect changes - SSH to Git on Azure

I'm periodically getting "unable to detect changes" to my Git repo via SSH. Its only occasional, and mostly overnight. During my working hours I get one or two throughout the day. Overnight there might be 30-40 notifications. 

I'm trying to interpret the error below to find out if this is a network/infrastructure issue or my configuration. As I say, this works most of the time. 

I find it odd that the git ls-remote is trying to connect to 127.0.0.1. Is the network disconnected?

Is there a notification I can modify to make this report less.


com.atlassian.bamboo.plugins.git.GitCommandException:
command ['C:\Program Files\Git\cmd\git.exe' ls-remote ssh://<removed>@127.0.0.1:63791/<removed path>]
failed with code 128.
Working directory was [c:\Program Files\Bamboo\temp]., stderr:
Remote connection failed stdout: Warning: Permanently added '[127.0.0.1]:63791' (RSA) to the list of known hosts. BAMBOO-SSH-PROXY: [SSH proxy tried to connect to [git@ssh.dev.azure.com/51.104.26.0:22]:
and failed due to the following error: [Remote connection failed]: Failed to get the session.] fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events