Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The build process should not rely on extremely long paths #2550

Open
corranrogue9 opened this issue Nov 11, 2022 · 0 comments
Open

The build process should not rely on extremely long paths #2550

corranrogue9 opened this issue Nov 11, 2022 · 0 comments
Labels
infrastructure build environment, engineering system and other things for developer productivity. P3

Comments

@corranrogue9
Copy link
Contributor

The OData.sln, OData.E2E.sln, and OData.Pipeline.sln solutions fail to build if the repo is cloned in a path that is too long. I don't know the limit, but I know that if you clone the repo into a path that is 57 characters (such as c:\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa), this build failure will reproduce.

  1. We should not require such long paths during build in the first place
  2. Where we do require long paths, we should only be using build utilities that support those long paths (rather than ones that fail to find the files in those paths and produce build failures)
  3. When these two issues are addressed, the onboarding .md files in the sln folder should be update to remove their suggestion to use a very short path as the root of the onboarder's repo
@KenitoInc KenitoInc added P3 infrastructure build environment, engineering system and other things for developer productivity. labels Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure build environment, engineering system and other things for developer productivity. P3
Projects
None yet
Development

No branches or pull requests

2 participants