jeantil commented on PR #2845: URL: https://github.com/apache/james-project/pull/2845#issuecomment-3489573236
sorry its been busy lately Unfortunately a green build on master would probably not fix the invalid cache entry (since the build cache there is disabled and when you enable it again it will start using the cache again and unless there has been a change on the corresponding module it will be pulled from the cache) In case there is an invalid cache entry the quick way to clear it is to add `-DrerunGoals` to the maven opts https://docs.gradle.com/develocity/maven-extension/current/#rerunning_goals This will not help understand how the bad cache entry was stored but it will unlock CI. Understanding the cause of the bad cache entry requires doing detailed input analysis on the task that generated the bad entry. My first suspect would be the custom cache config for both scala and jacoco that I added and I could very well have ignored something that shouldn't be ignored. One can hope that the config for the default plugins which is provided by develocity is correct but I'm not sure how much adoption it has so even this may have bugs. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
