git checkout fails due to windows path length restriction

Our .net source folder structure ends up with some very long file paths (think \verylongsolutionname\verylongprojectname\Service References\verylongservicename\verylongprojectname.verylongservicename.datasource). This code is (currently) autogenerated through visual studio, so changing them to short names would be a large task with continual maintenance.

This limits us when cloning the repository to quite short repository paths. When bamboo checks out the version it tries to do so into something like this "bamboo-home\xml-data\build-dir\HZN-DEV-JOB1" it fails because it's violating windows 260 char limit. I'm guessing this sort of path structure is hard coded, so I can't just get it to clone into c:\shortpath or similar...

Has anyone overcome this sort of issue?

1 answer

We had a problem with the build not the checkout so it was a bit easier to handle. I made a symlink to bamboo-home\xml-data\build-dir and always used that.

Suggest an answer

Log in or Join to answer
Community showcase
Jason Wong
Published yesterday in Agility Beta

Welcome to agility

Every team in the world is unique, and so   Atlassian believes   that each and every team's best way of working  needs to  be molded to their unique circumstances  – ...

237 views 5 14
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot