Xavier Hanin wrote:
What you do is what we call in Ivy "changing" revisions. If you configure
Ivy properly, you should be able to let Ivy do its cache management
itself,
with no need to do a manual clean up. Then you will only download what
has
What is 'configured properly' in this case ?
actually changed, which could improve your build significantly.
Moreover, if
your frequent builds are done on your CI system, maybe you can use
useOrigin="true" on the CI system, so that the copy to the cache can be
avoided. Does it make sense in your situation?
-- stephane
