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 Sign up to answer
Community showcase
Published 10 hours ago in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

152 views 0 5
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