[
https://issues.apache.org/jira/browse/MBUILDCACHE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878185#comment-17878185
]
ASF GitHub Bot commented on MBUILDCACHE-104:
--------------------------------------------
AlexanderAshitkin commented on PR #175:
URL:
https://github.com/apache/maven-build-cache-extension/pull/175#issuecomment-2321856106
The distribution is a good example. However, what's unusual here is an
attempt to distribute a single-module build. The zones are intended to divide
the build into smaller, shareable parts, but there is already a mechanism for
that - the projects themselves. The projects (modules) exist to make the build
more manageable and optimized by splitting the project into smaller parts.
Smaller projects allow more efficient results sharing as well.
I can see the value in this change, but it take some time to evaluate the
idea, tradeoffs and options.
> Allow multiple cache entries per checksum
> -----------------------------------------
>
> Key: MBUILDCACHE-104
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-104
> Project: Maven Build Cache Extension
> Issue Type: New Feature
> Reporter: Réda Housni Alaoui
> Priority: Major
> Labels: pull-request-available
>
> I have the following use case: a CI pipeline with a compile step *then*
> multiple parallelized test steps. Tests are split in 3 groups. Each test
> group execution specify the group via maven-surefire-plugin:test property
> 'groups'.
> Maven phase for compilation: process-test-classes
> Maven phase for tests: verify
> The compilation should use remote cache as much as possible and end up
> populating it.
> Each test execution should either use the populated cache ending with
> process-test-classes phase or a cache representing the result of the
> execution of the current test group (value for 'groups').
> The issue I have is that this extension can only store a single cache entry
> per input checksum. But I need to persist the build result of each test group.
> The easiest solution I can think of is having 4 cache zones. The first for
> the compile phase (the default zone), the 3 remaining for each test group.
> I need the compile phase to read/write from/to the default cache zone.
> I need each test group to read from its own cache zone then the default cache
> zone, *in this order*. At the end, it should write to its own cache zone.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
