From 10271a50c8f186795fc35f0a765759d16459ce99 Mon Sep 17 00:00:00 2001
From: Benjamin Pannell <admin@sierrasoftworks.com>
Date: Fri, 31 Jul 2015 11:40:04 +0200
Subject: [PATCH] Added fixes for PathTooLongException to FAQ doc

---
 docs/faq/README.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/docs/faq/README.md b/docs/faq/README.md
index bca46bbad..ee8d6a963 100644
--- a/docs/faq/README.md
+++ b/docs/faq/README.md
@@ -12,3 +12,21 @@ Is it possible to run GitLab Runner in debug/verbose mode. Do it from terminal:
 ```
 gitlab-runner --debug run
 ```
+
+## 3. I get a PathTooLongException during my builds on Windows
+
+This is caused by tools like `npm` which will sometimes generate directory structures
+with paths more than 260 characters in length. There are two possible fixes you can
+adopt to solve the problem.
+
+### a) Use Git with core.longpaths enabled
+
+You can avoid the problem by using Git to clean your directory structure, first run
+`git config --system core.longpaths true` from the command line and then set your
+project to use *git fetch* from the GitLab CI project settings page.
+
+### b) Use NTFSSecurity tools for PowerShell
+
+The [NTFSSecurity](https://ntfssecurity.codeplex.com/) PowerShell module provides
+a *Remove-Item2* method which supports long paths. The Gitlab CI Multi Runner will
+detect it if it is available and automatically make use of it.
\ No newline at end of file
-- 
GitLab