[
https://issues.apache.org/jira/browse/MBUILDCACHE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Réda Housni Alaoui updated MBUILDCACHE-104:
-------------------------------------------
Description:
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 remote cache zones. The first
for the compile phase, the 3 remaining for each test group.
I need the compile phase to read from the first remote cache zone and *write to
all cache zones*. I need each test group to read/write from/to their respective
cache zones.
I propose to split the remote cache configuration between readable cache and
writable cache and to allow multiple remote cache locations.
was:
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 remote cache zones. The first
for the compile phase, the 3 remaining for each test group.
I need the compile phase to read from the first remote cache zone and *write to
all cache zones*. I need each test group to read/write from/to their respective
cache zones.
I propose to split the remote cache configuration between readable cache and
writable cache and to allow multipl remote cache locations.
> Allow to distinguish 2 kinds of remote cache url: one for read and one for
> write
> --------------------------------------------------------------------------------
>
> 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
>
> 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 remote cache zones. The first
> for the compile phase, the 3 remaining for each test group.
> I need the compile phase to read from the first remote cache zone and *write
> to all cache zones*. I need each test group to read/write from/to their
> respective cache zones.
> I propose to split the remote cache configuration between readable cache and
> writable cache and to allow multiple remote cache locations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
