[
https://issues.apache.org/jira/browse/LUCENE-10195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434401#comment-17434401
]
Dawid Weiss commented on LUCENE-10195:
--------------------------------------
{quote}You might be interested by the [--rerun-tasks
option|https://docs.gradle.org/current/userguide/command_line_interface.html#sec:rerun_tasks]
which allow to ignore up-to-date checks.
{quote}
This reruns all tasks in the graph which is more of a pain than help (in
majority of cases :)). To me the absolutely best feature of gradle lies in
incremental tasks. When things are configured correctly this means
incremental-check subsystem pretty much takes care of itself. I almost never
have the need to run a full 'clean'.
{quote}Sorry, maybe i wasn't clear. It is my understanding, that by default, it
could cache 2MB in the local cache and it would persist across "gradle clean".
{quote}
It would still try to run this task on the first run when the input/output
information isn't locally available (assuming no external cache is provided).
This means it'd run at least once. To me this is a no-go. I really wish there
was a mechanism for somehow persisting the state of up-to-date checks but there
isn't.
> Gradle build speed improvement
> ------------------------------
>
> Key: LUCENE-10195
> URL: https://issues.apache.org/jira/browse/LUCENE-10195
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Jerome Prinet
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Increase Gradle build speed with help of Gradle built-in features, mostly
> cache and up-to-date checks
>
--
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
