4 ms·
I agree, tracking down a failed CI build that ends up being a cache problem is much more frustrating to me than waiting a little longer for the build.
by dannyz 5y ago
I agree, tracking down a failed CI build that ends up being a cache problem is much more frustrating to me than waiting a little longer for the build.
- sharken 5y agoThe attention to pipeline speed is great, i don't think I have seen anything this detailed before. Having implemented a pipeline cache to reduce wall time with 15 minutes for each execution, i wouldn't want to go back to no cache. But it's important to be resilient to a faulty cache. If that is hard to achieve, then it makes good sense to avoid caching.
- maccard 5y agoWe cache builds on my work c++ projects. A clean build would be 2+ hours, using cached artifacts is about 5 minutes.
- dnsmichi 5y agoCan you share more details about the size of the project (files count, build file size) and which caching settings you are using? I assume it is ccache and am curious how you use it.
- maccard 5y agoIt's a ue4 based game project. Unsure of the size offhand, sorry (and it's Sunday, so I'll check tomorrow). > I assume it is ccache and am curious how you use it. Nope. We just use the same machines for the same jobs (we have 3 agents, and we use teamcity which lets us pin our configurations to agents), and incremental builds. Really basic stuff. The machines are managed by terraform and packer and we rebuild the images once a month or so, so semi frequently pay the full compile hit. I am going to look into actual persistent caching for Mac very soon, it's likely we'll go with fastbuild!