[
https://issues.apache.org/jira/browse/IGNITE-29134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Amelchev updated IGNITE-29134:
-------------------------------------
Description: The javadoc check of the commit-check workflow installs Ignite
modules into the local Maven repository, so setup-java saves their snapshot
jars into the Maven cache along with third-party dependencies. Every run
rebuilds these modules anyway, so the cached copies only enlarge each cache
entry and let a build silently resolve stale Ignite classes of another commit
instead of the reactor ones. (was: The commit-check and Sonar workflows cache
the same {{~/.m2}} under different keys, so each pom state is stored twice (500
MB and 792 MB entries) and the repository sits at 9.96 GB of the 10 GB cache
quota. The larger entry is inflated by Ignite snapshot jars installed by the
build itself, which are stale for any other run. Use a single key across the
workflows and exclude Ignite snapshots from the cached path.)
> Build javadoc in the commit-check workflow without installing Ignite modules
> ----------------------------------------------------------------------------
>
> Key: IGNITE-29134
> URL: https://issues.apache.org/jira/browse/IGNITE-29134
> Project: Ignite
> Issue Type: Improvement
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The javadoc check of the commit-check workflow installs Ignite modules into
> the local Maven repository, so setup-java saves their snapshot jars into the
> Maven cache along with third-party dependencies. Every run rebuilds these
> modules anyway, so the cached copies only enlarge each cache entry and let a
> build silently resolve stale Ignite classes of another commit instead of the
> reactor ones.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
