- Version: SonarQube Enterprise 188.8.131.52792, Azure DevOps (cloud hosted)
##[error]08:27:57.65 Failed to create an empty directory 'D:\[path]\[path]\221\.sonarqube\out'. Please check that there are no open or read-only files in the directory and that you have the necessary read/write permissions.
- Detailed error message:
Could not find a part of the path 'D__[path]_[path]_221_s_[appname]_src_web_apps_WebHealth_wwwroot_lib_jquery_validation_unobtrusive_jquery_validate_unobtrusive_js_288_23_FE_18_ada_min_max_min_min_max.ucfg'.
- Steps to reproduce: intermittent, but happening pretty regularly now
- Work-around: unknown
We started seeing this with one of our projects when it was updated from .NET Core 3.1 to .NET 5. However, that commit didn’t make any changes to the UI, which is where the file name is coming from.
The error is the same in all cases - when it happens - but there are different results I’m seeing.
- Most of the time, that absurdly long file name is there (in a pretty deep path). I cannot rename it or delete it in a normal manner, and end up having to use robocopy d:\ . /purge from the directory to delete it
- Some of the time, I go there and the directory is empty. I end up just deleting the .sonarqube folder for that pipeline, and the next time it runs, it is successful
Three questions: (1) why is it creating such long file names (including part of the path), (2) why is it creating such a deep path, which exacerbates the problem, and (3) what, if anything can I do about it to get these builds working consistently again?
The path where that long file name gets created looks like this: