Op 03-05-2021 om 11:08 schreef Andrea Aime:
Any objection to removing all the prefixes from the database QA builds?
That should reduce the cache count significantly.
It's true that this could cause a cache to start small, due to a
database build not hitting all modules, but in a few rounds
of builds it should grow to handle everything (it's not like we change
the pom files every other day).
Another angle to look at this would be, do we really need per OS caches?
Again, I don't think we need OS specific
caches, do we?
In the back of my mind I knew there were limits on cache size, but
didn't know about the total size per repo... but reading
https://docs.github.com/en/actions/guides/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy
says so as well, 5GB total, cache is preserved for a week.
It would make sense to have the same key for all jobs (and OS-s as well)
then I think; any snapshot dependencies are removed before the cache
is build anyway.
Db2 and Oracle are already sharing a cache
-M
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
