[GitHub] [maven-build-cache-extension] eltsovalex commented on pull request #51: [MBUILDCACHE-48] - Add possibility to disable caching per module in a multi-module project

["eltsovalex (via GitHub)" <gi...@apache.org>]

eltsovalex commented on PR #51:
URL: https://github.com/apache/maven-build-cache-extension/pull/51#issuecomment-1497146448

   > Hi Alex. Regarding the code itself - looks good to me. But please clarify the use case and rationale for the change. Is it for cases where the local build is faster than downloading from the cache? I understand uploading might be expensive, but an existing configuration parameter allows for skipping the upload. And if uploading doesn't happen, I wonder what the benefits are achieved by disabling the cache compared to disabled upload. Thank you!
   
   Hi. Thanks for asking. Sorry for not providing a precise description of my use-case.
   So, I have a module in my project that builds a huge EAR of ~200Mb as a target. Due to some specific reasons (e.g. project version written deep down in one of jars inside EAR +some build artifacts required for publishing by CI to be present in target folder) I have to always build that subproject clean (so without caching). And while the previous flag I added last year (maven.build.cache.skipCache) works fine to solve the forced rebuild task - it still uploads the 200Mb EAR to cache. So it spoils the cache with multiple versions of a huge unused file + takes some time for the upload itself. As this is not an attached artefact, but a main goal - I can not add it to ignored/not uploaded.  
   Hence this new property added that totally disables cache on a per-project level (both lookup and upload) 


-- 
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-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org