[ https://issues.apache.org/jira/browse/MBUILDCACHE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875238#comment-17875238 ]
ASF GitHub Bot commented on MBUILDCACHE-104: -------------------------------------------- reda-alaoui opened a new pull request, #175: URL: https://github.com/apache/maven-build-cache-extension/pull/175 Following this checklist to help us incorporate your contribution quickly and easily: - [X] Make sure there is a [MBUILDCACHE JIRA issue](https://issues.apache.org/jira/browse/MBUILDCACHE) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [X] Each commit in the pull request should have a meaningful subject line and body. - [X] Format the pull request title like `[MBUILDCACHE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MBUILDCACHE-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [X] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [X] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ > 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 > > 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)