uschindler commented on code in PR #12293:
URL: https://github.com/apache/lucene/pull/12293#discussion_r1200514470


##########
gradle/ge.gradle:
##########
@@ -0,0 +1,26 @@
+def isGithubActions = System.getenv('GITHUB_ACTIONS') != null
+def isJenkins = System.getenv('JENKINS_URL') != null
+def isCI = isGithubActions || isJenkins
+
+gradleEnterprise {
+    server = "https://ge.apache.org";
+    buildScan {
+        capture { taskInputFiles = true }
+        uploadInBackground = !isCI
+        publishAlways()
+        publishIfAuthenticated()
+        obfuscation {
+            ipAddresses { addresses -> addresses.collect { address -> 
"0.0.0.0"} }
+        }
+    }
+}
+
+buildCache {

Review Comment:
   OK Thanks!
   
   To answer your question. On private workstations it should be kept disabled 
as it has some drawbacks:
   
   When it was enabled I needed to "rm -rf ~/.gradle/" almost daily in my 
homedir to get rid of tons of files. This was espeically a desaster when the 
Gradle build was "under development". There are also some people that disable 
the gradle daemon, because at same time their whole "ps" was filled with unused 
daemons (those people often run tests with different versions of JDK and all of 
them spawn separate sets of processes).
   
   At some point Gradle should clean up its caches correctly and sometimes 
delete old stuff, which seems not working at moment.
   
   The same by the way happened on above "Policeman Jenkins", it filled its 
Jenkins homedir with cached stuff and dies several times and due to gradle 
daemons for hundreds of Java versions it also filled its memory.
   
   I agree on coorporate environments it can be enabled, but people working 
from different parts of the world on a open source projects, over exxcessive 
caching stops progress. I have no problem with Gradle taking 2 secs longer on 
startup.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to