5 ms·
A huge portion of my actions are for things like caching or publishing artifacts, which are unique to actions itself.
by ghayes 3y ago
A huge portion of my actions are for things like caching or publishing artifacts, which are unique to actions itself.
- taeric 3y agoI'd assume you would be able to publish and deploy locally before setting up actions. Such that those are likely targets in your build system? Caching, I can mostly understand as unique there. Though, I think I'm living with whatever the default stuff in actions is. Slow for builds that don't happen often, of course, but not so slow that I care.
- Tainnor 3y agoUnfortunately, my team has some builds that take ~25 min without caching and maybe 2 min with caching. I'm still not entirely sure why it's the case, but the connection to the package registry is incredibly slow, so downloading all dependencies takes forever.
- taeric 3y agoI'm fortunate that worrying about 25 minute builds just doesn't matter. The long pole on all builds is still the code review that goes with it, such that I just don't care about getting that time too low here. That is, I am assuming that a CI build is not on the immediate dev loop, such that the person pushing it doesn't have to wait for the build before they prepare a review on it.
- duped 3y agoWhy should caching in the cloud be any different than caching locally?
- baq 3y agoThere isn’t any locally in GHA after the runner exits