[GRADLE-1167] $HOME/.gradle/<version>/scripts never gets cleaned out Created: 07/Oct/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Bug
Reporter: Vince Rosso Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Gradle creates a directory for compiled scripts in $HOME/.gradle/<version>/scripts for each project. A unique project is defined by the path of the project src directory. It seems that these are never cleaned out. Most filesystems have a subdirectory limit (e.g. a directory can't hold more than 32768 subdirectories in EXT2). Once that limit is reached, gradle will refuse to compile any new projects.

My company has an automated build system that periodically checks out our products from SVN into a different tmp directory each time. So, we're creating a lot of these cached script directories and running into the limit pretty quickly.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:48:40 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.