nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Important! Windows Runner build can have a shorter path?

Valeriu Ghisoiu

Hello Atlassian,

Can we overcome the long name folders where the build is cloned from the remote repo in the CI/CD pipelines? It makes my paths of the deepest files to have 259 paths in Windows.
The maximum is 260 (even if I enable the long paths is not working) (Windows limitations).

eg: C:\CICD\tmp\{runner-uuid}\8547119988257\build

Can we at least make the folders names shorter??? (I can use only 7 characters CICD\tmp . This is not ideal.

Need BIG HELP on this, I can't rename the files in submodules.

Warm regards,

Valeriu

Accepted answers

All comments

Theodora Boudale

Hi Valeriu,

The part after C:\CICD\tmp in the path is the UUID of the runner (just a heads up, I edited it in your post for privacy reasons). The part 8547119988257 is based on the EPOCH time when the build starts. These parts cannot be edited, however there are ways to resolve the issue.

You can configure Git on your Windows machine to allow paths of 4096 characters. You can do this by running the following command from Git Bash or another terminal application:

git config --global core.longpaths true

This config will apply to the currently logged in Windows user, since it has the --global flag.

Another option is to change the default 260 character limit in the Windows registry. You can read more info on how to do this here:

https://confluence.atlassian.com/bamkb/git-checkouts-fail-on-windows-with-filename-too-long-error-unable-to-create-file-errors-867363792.html

This knowledge base article is about Bamboo, but it concerns the same issue, so the info there should help with the issue on Bitbucket's Windows runner.

Please feel free to let me know if this helps or if you're still facing issues.

Kind regards,
Theodora

Valeriu Ghisoiu

Hello Theodora,

Thank you very much for all the help and suggestions, and also for editing the sensitive data.

Luckily or Unfortunately everything that you proposed I already tried.

This is why I ended up here as a "last hope".

I added "git config --global core.longpaths true" in my yaml file
I changed the windows registry to use long paths and all solutions searched.

Unfortunately I found out that Microsoft Windows solved in 2024 only half of the issue, because they didn't update the API for File Manager (file explorer) to really use the long paths, so it is still limited to 260.
This means that powershell, cmd are using maximum 260.
This is the reason why I asked Atlassian if there is any possibility to shorten the path of the runner temporary file .

I only have 7 characters left up to 260 and is not enough.

Maybe there is a possibility that the runner is using something like Total Commander instead of Windows file Manager and that will solve the issue, because TC has the updated API of windows with longpaths.

I hope and wish so much to help me with this matter and also I think it is very important for Atlassian if can offer a help or work-around on this matter it can win a lot in front of other competitors.

Looking forward to your answer.

Kind regards,
Valeriu

Theodora Boudale

Hi Valeriu,

I have tested the solution with

git config --global core.longpaths true

and it works well for me as long as the path is less than 4096 characters.

I would like to ask a few questions:

1. Is the longest path of your files less than 4096 characters or is it longer?

2. If you log in to this Windows machine with the Windows user you use to log in to start the runner, can you check the file .gitconfig in the home directory of this user? Does this file contain an entry like the following?

[core]
    longpaths = true

If not, can you execute the command git config --global core.longpaths true on PowerShell, outside of the runner?

Then ensure that the entry is in the .gitconfig file, and run another build. Do you see the same error that the filename is too long?

3. What version of Git and PowerShell are you using on this machine, and what is the version of Windows?

Kind regards,
Theodora

Valeriu Ghisoiu

Hi Theodora,

Let's break it down.

1. Yes it is less, more exactly I would need 280-300 characters, I tried to minimize and it was working for 259 (but I don't want to use locations like C:\a\b\c That is impossible to work . I am working on windows 11 and 10, both didnt work

2. Yes it exists there already, (along side other core options or a path to OpenSSH - hope is not influencing). I ran the runner on 3 different computers with windows and enabled long paths in windows and git, none was working (

3.

- Git version 2.38.1.windows.1

- powershell 5 (the basic from windows 11/10)

- Windows 11 (and also tried on windows 10).

(Are the same versions for you too?)

Kind regards,

Valeriu

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket-cloud

windows

yaml

runner

pipelines

cicd

windowsrunner