[
https://issues.apache.org/jira/browse/LUCENE-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183428#comment-17183428
]
Uwe Schindler commented on LUCENE-9474:
---------------------------------------
Another option would be to configure jobs to initially run an additional gradle
run just calling the defauts task. This would generate the gradle.properties
file and then exit. The main run would then pick the previously generated file
and use all 3Gigabytes of heap and correct number of workers.
Can I tell the default task to create a config to saturate the CPU as much as
possible. Currently I set workers=tests.jvms=numberofcpus
Another option would be the Groovy environment plugin calling
System.getRuntime().numberOfProcessors() and persisting it to a property passed
to gradle.
> Change Jenkins jobs to use Gradle for trunk
> -------------------------------------------
>
> Key: LUCENE-9474
> URL: https://issues.apache.org/jira/browse/LUCENE-9474
> Project: Lucene - Core
> Issue Type: Test
> Components: general/build
> Reporter: Erick Erickson
> Assignee: Uwe Schindler
> Priority: Major
>
> I rushed the gate and pushed LUCENE-9433 without coordinating, my apologies
> for the confusion.
> Meanwhile, Uwe has disabled Jenkins jobs for the weekend and we'll fix this
> up Real Soon Now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
