https://pact.io logo
Join Slack
Powered by
I've hit the windows long path issue in CI, where ...
# pact-js
t
I've hit the windows long path issue in CI, where I don't have much control over what the path is. Has anyone got any tips for working around this?
😱 2
a
Have no prior experience on the issue, but my immediate though of a dumb workaround would be to symlink the target files to some shorter path. Can't remember how those were processed on Windows and whether a symlink will resolve to the full path when being accessed, but at least I'd expect hard links would work if you can create those in the CI 🤔
🤔 1
t
I like this idea. Looks like I can't break out of the 
{repo-name}/{repo-name}
path on github actions, or my windows fu isn't good enough (possibly both)
I guess a workaround could be to rename the repo, but that seems extreme (and it's public, so I kinda dont want to)
you can give github actions a working directory, but it puts it at the end: 
{repo-name}/{repo-name}/{working-dir}
, and you can't use 
..\..\
m
What if we allowed the location of the standalone installation to be customised? e.g. rather than embedded in the project folder, we allowed it to be put in 
c:\Temp
?
I think that should sidestep the problem?
t
I think that's a good idea, but I think it won't work for my situation, which is that I don't seem to have permissions anywhere other than the doubled repo name
I worked around it by disabling windows builds
...not ideal, but it's not a huge problem in my case. However, this might affect other users of github actions who need windows builds
👍 1
m
What do you think about the idea of changinsg the install path?
t
I think it will help some people, but I think it might be more trouble than it's worth
👍 1
depends how far away the rust core is
👍 1
I think changing the install path won't work for CI
and for non-CI changing the project path is largely ok
👍 2
Open in Slack
PreviousNext
Powered by