Hacker News Reader

Bingo 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.

View on HN

Author 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-w...

That 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.

Reply on news.ycombinator.com