This message was deleted.
# develocity
s
This message was deleted.
c
By default, outputs are stored in the local Build Cache if it is enabled and the build includes the
clean
lifecycle phase. The cache is enabled, but can you see if adding the clean lifecycle (i.e.
mvn clean package
) solves your problem?
j
clean is mandatory ? that was not clear for me thanks
the cache is enabled
thanks
c
Clean is mandatory if you want to store cache entries. This is for safety - we need to know that a particular execution of a goal created certain outputs and to make sure that they weren't present from a previous build. The cache can work in a read-only mode without clean.
j
indeed rereading the getting started I cans ee the info section https://docs.gradle.com/enterprise/maven-build-cache/#getting_started I suggest turning that into a warning šŸ˜„ I am used to gradle's cache where I don't need clean šŸ˜„
šŸ‘ 1
much better !
šŸ™Œ 1
cached build went from ~4 min to ~1 min
c
Nice!
When you get ready to make a PR for this Apache project, feel free to request a review from me. We have connected a number of Apache projects to ge.apache.org, so we are glad to help.
j
thank you, I intend to connect this iteratively first the build scans and the local cache my experiments show we have several mojos with unsupported goals and scala compilation in particular I already tried adding configuration for this mojo but the results were not good with compile errors once caching is enabled so I guess my inputs/outputs are not properly documented but the documentation is very sparse on this. I used several code samples found in develocity and more generally in github top try and set this up but none were for scala and clearly something is amiss
c
We have a number of samples here on making certain Maven goals cacheable, but yes, none for the
scala-maven-plugin
. I will ask around with some of my colleagues if we have encountered it before, and if not, we could possibly provide a similar sample.
j
I was forced to exclude things that I feel should not be excluded because develocity reported errors about complex objects : • 'compilerPlugins' contains unsupported type: File. https://ge.apache.org/s/ogqqipianlfo4/timeline?cacheability=any-non-cacheable&detai[…]xecution=sca&hide-timeline&outcome=success,failed&sort=longest • dependencies' contains unsupported type: Dependency. • 'pluginArtifacts' contains unsupported type: DefaultArtifact. • etc and each time I have to run a build to get the next error (would be nice if it listed all that's wrong in one go šŸ˜„
anyways thanks for your help