Why can't SourceTree complete a clone using either ssh or http?

SourceTree will fail a clone at the exact same file using ssh or http.  Only 46% of 14,211 files are obtained.  it it theorized here that SourceTree is choking on a path name that is heinously long.  Here is the path that fails with the attendant prepended and appended error strings:

error: unable to create file ui/middleware/node_modules/sequelize-cli/node_modules/gulp/node_modules/gulp-util/node_modules/dateformat/node_modules/meow/node_modules/normalize-package-data/node_modules/is-builtin-module/node_modules/builtin-modules/builtin-modules.json (No such file or directory)

Cloning from the command line works always.  This fails in the exact same place every tine no matter which protocol is used (so obviously not protocol dependent).

This is SourceTree on Win10 with repository and client on CentOS systems.

1 answer

When you begin your clone, you can select "Show Full Output" to see the exact git command that SourceTree is running. You might try copying that command verbatim to the command line.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Oct 23, 2018 in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

961 views 4 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you