reda-alaoui commented on PR #175: URL: https://github.com/apache/maven-build-cache-extension/pull/175#issuecomment-2315535102
> Different plugin parameters result in different hash sums, and these different checksums are stored separately. This is only true if the plugin parameter is tracked by the effective pom. By default, it is not the case. Plus I track those parameters via the reconciliation tag. > 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. I want a `test group` step to resume where the `build` step ended. If the checksums are different between the 2, that's not possible. My CI flow is `compile -> parallel[test group 1, test group 2, test group 3]`. Each `test group` step should skip any plugin execution already performed by `compile` step. > 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. When I said `persist the build result of each test group`, I was meaning that running one of the test group again, without any code change, should skip all plugin executions. -- 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
