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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

we are getting the following error during jenkins build


ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "git fetch --tags --progress +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stderr: Warning: Permanently added ',XXXXX' (RSA) to the list of known hosts.


fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed


1 answer

0 votes
Syahrul Atlassian Team Apr 12, 2022

G'Day @sivakumar karthikesan 

Welcome to the community!

The error you are seeing can be caused by multiple reasons such as:

  1. Large repositories
  2. Network
  3. Jenkin bug

I would suggest starting with your repositories size, if it's larger than 1GB tried to reduce the size further and create a support ticket to trigger GC.

As for the network, this is very hard to investigate since it requires an in-depth network investigation to understand why the connection is dropped. If you have any firewall/proxy in between your server and external network I would suggest you start from there.

Regarding Jenkin Bug, I did notice a recent bug/issue raised by one of the Jenkin users reporting having an issue cloning repositories after they upgrade the Jenkin/plugin version at:

I hope this helps!


Thank so you for the detailed explanation. just trying to understand as we have many branches will that too cause the issue?

Syahrul Atlassian Team Jun 14, 2022

Hey @sivakumar karthikesan 

Yes, having hundreds of branches can be a cause of this issue as well. So it's advisable to always delete the branch you no longer used.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events