[
https://issues.apache.org/jira/browse/MBUILDCACHE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956941#comment-17956941
]
Olivier Lamy commented on MBUILDCACHE-94:
-----------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-build-cache-extension#323|https://github.com/apache/maven-build-cache-extension/issues/323].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> Provide a build cache report on builds
> --------------------------------------
>
> Key: MBUILDCACHE-94
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-94
> Project: Maven Build Cache Extension (Moved to GitHub Issues)
> Issue Type: Improvement
> Reporter: Marquis Wang
> Priority: Major
> Labels: pull-request-available
>
> When building with the build cache, it would be really helpful to provide a
> report of which modules were unable to utilize and cache, as well as
> information about why.
> Right now, when looking at build cache performance, we can use
> {{maven.build.cache.failFast}} and {{maven.build.cache.baselineUrl}} to
> understand which module(s) were unable to utilize the build cache and why.
> However, this process is entirely manual.
> It would be really helpful to provide some base cache statistics on every
> run, even if no baselineUrl is provided. That way, we can gather overall
> statistics and figure out how to change our project to better utilize the
> cache.
> For example, we have a multi-module project with hundreds of modules. I want
> to know if there is one module that is constantly changing and is depended on
> (possibly unnecessarily) by lots of other modules, which is causing cache
> misses.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
