AlexanderAshitkin commented on PR #175: URL: https://github.com/apache/maven-build-cache-extension/pull/175#issuecomment-2315327113
> Of course, I can still open a discussion on the mailing list for such a large change. I'm trying to understand that is causing issues and what type of issues it is, in this case with different `<groups>` plugin parameters. > The problem I'm facing is that the extension can only store one cache entry per input checksum, but I need to save the build result of each test group. Different plugin parameters result in different hash sums, and these different checksums are stored separately. If there are 3 different build configurations (though profiles or command line parameters) with 3 different groups, it yields 3 different cache records under different checksums. This makes different checksums equivalent to different zones. Another point that's unclear to me is the statement: > But I need to persist the build result of each test group. I don't see any problem using classifiers or some other method to differentiate artifacts stored in the build. If we split build in logical parts, we must consider the case of the next plugins, which depend on the "zoned" cache records. And it must run consistently with the non-cached build. From what I understand now, this scenario is already supported. There are two options: 1. Having 3 different runs with 3 different groups resulting in 3 different cache records under different checksums. 2. Within a single build, using the same checksum but storing the results using group-specific classifiers. We also should consider, that if the plugins in questions are not leaf plugins. Overall, I would like to better understand the problem, starting with the build configuration and the use case. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
