-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
I am using sparse-checkout functionality of git-plugin for most of the projects. However it's quite often that commits are modifying different directories (e.x. moves) and this gives a failed build with message like:
Caused by: hudson.plugins.git.GitException: Command "git checkout -f xxx" returned status code 128:
stdout:
stderr: error: Sparse checkout leaves no entry on working directory
There should be an option to handle cases like that - preferably give the ability to choose between displaying good error message or doing non-sparse checkout.