3 ms·
If a build takes 4 hours it argues that a build on that system is a pretty expensive operation, unless changes are very infrequent, which in most systems is not
by bryanrasmussen 7y ago
If a build takes 4 hours it argues that a build on that system is a pretty expensive operation, unless changes are very infrequent, which in most systems is not the case, a build run on every change would seem to be highly problematic.
- tlarkworthy 7y agoBingo it's expensive, which is why they set it to every 24 hours. Also coz they don't want to add the queuing logic, so it takes 4 hours to run is an approximation. Also it messes with other systems so they prefer to run it overnight. This blog doesn't solve a real problem.
- royosherove 7y agoAuthor here. It's literally the first line in the blog post. And it links to this blog post about static environments: https://pipelinedriven.org/article/the-four-biggest-issues-with-having-static-environments https://pipelinedriven.org/article/the-four-biggest-issues-w...
- tlarkworthy 7y agoThat doesn't answer anything. Either you: minimize latency (run every change independent of build time) or run to minimize engineering (24 hours). I dunno why you couple build time to a static period, it does not make sense to me.
- lonelappde 7y agoBuilds are cheap compared to running in production. Stop being a cheapskate.
- bryanrasmussen 7y agoI don't understand your running in production comment in this context, nor actually your stop being a cheapskate aimed at me.