# Configure pipline pull request path

**URL:** <https://community.jenkins.io/t/configure-pipline-pull-request-path/4864>\
**Category:** Using Jenkins\
**Tags:** windows, pipeline\
**Created:** [December 7, 2022, 10:50am UTC](https://community.jenkins.io/t/configure-pipline-pull-request-path/4864 "2022-12-07T10:50:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![antispam88](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/antispam88/32/2866_2.png) [@antispam88](https://community.jenkins.io/u/antispam88)\
**Post date:** [December 7, 2022, 10:50am UTC](https://community.jenkins.io/t/configure-pipline-pull-request-path/4864/1 "2022-12-07T10:50:46Z")

</div>

Hi,  
we are using Jenkins’ pipeline to build our project.  
The project uses Bitbucket as source control.  
We have also included files for unit testing in the repository.  
For normal branches the system is working, but with pull requests we are getting the error “Filenname too long” while checking out the files for unit testing.  
The problem is that in case of pull requests Jenkins uses a path \*\PR-1\WS}@script\ID where ID is 64 digit hex number as root directory.  
I know that there is a option to activate long file names in Windows but in our last installation I can remember that we had configured Jenkins or a plugin of it not using this 64 digit nex number but using the script directory directly as root.  
Can someone please help me.  
Best regards  
antispam

Windows: 10 Pro 22H2 x64  
Jenkins: 2.375.1 LTS

---

<div class="post-metadata">

**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\
**Post date:** [December 7, 2022, 1:07pm UTC](https://community.jenkins.io/t/configure-pipline-pull-request-path/4864/2 "2022-12-07T13:07:04Z")

</div>

Hi @antispam88 and welcome to this community 👋

Would the plugin you used be this one?

> **[Short Workspace Path](https://plugins.jenkins.io/short-workspace-path/)**
>
> Use shallow directory hierarchy for build workspaces to avoid failures on filesystems with constrained path length

---

<div class="post-metadata">

**Author:** ![antispam88](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/antispam88/32/2866_2.png) [@antispam88](https://community.jenkins.io/u/antispam88)\
**Post date:** [December 13, 2022, 10:11am UTC](https://community.jenkins.io/t/configure-pipline-pull-request-path/4864/3 "2022-12-13T10:11:12Z")

</div>

Thank you for your hint, but this plugin I haven’t used.  
In meantime I have got the solution.  
It wasn’t a plugin or a jenkins configuration, but it was the git configuration:  
`git config --global core.longpaths true`

Best regards  
antispam

---

<div class="post-metadata">

**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\
**Post date:** [December 13, 2022, 2:15pm UTC](https://community.jenkins.io/t/configure-pipline-pull-request-path/4864/4 "2022-12-13T14:15:44Z")

</div>

Thanks a lot for your feedback @antispam88 🙏