Consider using user cache for dev builds about arcade HOT 3 CLOSED

Jared additionally commented

I definitely agree with the philosiphy of keeping CI the same as developer environment as much as possible. That being said we've found a couple of places that differ for pragmatic reasons:
CI redirects %TEMP% to be under the git clone. This is to avoid overflowing temp directories on Jenkins runs and ensuring workspace cleanup actually cleans up.
CI always generates binary logs during build while developer builds do not. This slows things down a bit but makes failure investigation much easier.
CI always uses a bootstrap compiler. This isn't done locally because it adds ~5 minutes to the build time.
CI uses completely clean NuGet package cache in one leg, but re-uses caches inanother. Developer always re-uses caches.
These do cause occasional gaps between CI and developer workflows. But it's very rare and the trade offs are largely considered worth it in these cases.

from arcade.

Current official build work is updating this to use the user cache for dev work, and working folder for ci / official builds. The change will come in as part of the official build PR

from arcade.

dev builds now use user cache

from arcade.