[
https://issues.apache.org/jira/browse/MBUILDCACHE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877450#comment-17877450
]
ASF GitHub Bot commented on MBUILDCACHE-104:
--------------------------------------------
AlexanderAshitkin commented on PR #175:
URL:
https://github.com/apache/maven-build-cache-extension/pull/175#issuecomment-2315693656
1.
> My CI flow is compile -> parallel[test group 1, test group 2, test group 3]
2.
> was meaning that running one of the test group again, without any code
change, should skip all plugin executions.
Please clarify:
- Does statement 2 imply that the rerun is a different reactor `compile ->
test group 1` and the expectation is that the results of the initial run are
reused?
- Or does it mean you rerun as `compile -> parallel[test group 1, test group
2, test group 3]` and expect `compile, test group 2, test group 3` to be reused
from the cache?
- Does `parallel[test group 1, test group 2, test group 3]` refer to three
different reactor modules running tests?
- Are `compile` and any of `test group 1, test group 2, test group 3` parts
of the same module?
> This is only true if the plugin parameter is tracked by the effective pom.
You can move the parameter to the effective pom. One way to do this is by
using a profile that defines a literal property value and referencing that
value in a plugin. By doing so, the value will be interpolated to the plugin
parameters and become part of the effective pom.
> 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)
