Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


fatal: could not read Username for '': No such device or address

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 17, 2023

We have a Jenkins pipeline that checks out the code from This has been working fine for the last 3-4 years, but started failing over the weekend with the error "fatal: could not read Username for '': No such device or address".

The issue does not occur during checkout, that seems fine, but instead when we run the command "git fetch --prune --prune-tags origin" on the checked out workspace.

We found a solution to include the username and password in the URL, which is fine, it seems to work, but various posts on here seem to suggest switching to SSH keys instead.

  1. Why did it break? We did not update any software.
  2. Is the a good solution, or should we be looking to move to SSH for longevity?


1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 17, 2023

G'day @stuart_stephen 

Welcome to the community.

I have reviewed the recent changes and existing customer reports, and I can confirm that there have been no recent changes or reports of customers experiencing the same issue.

However, it's challenging to pinpoint the exact cause since the Jenkins server is hosted on your end. That said, I can confirm that using username:app_password behavior aligns with the expected outcome when using HTTPS.

To prevent similar issues in the future, I recommend switching to SSH.

I hope this information is helpful.


Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events