3 ms·
Curious what the HN community feels is a "slow deploy". I scanned the article first to find time reductions and still couldn't see how much time was actually ta
by nstart 7y ago
Curious what the HN community feels is a "slow deploy". I scanned the article first to find time reductions and still couldn't see how much time was actually taken at the end of it.
11 minutes is a great time reduction. (11*30 builds a day = 5.5 hours saved in total).
But I still am not sure what constitutes as a slow builds. I assume at some point there's an asymptotic curve of diminishing returns where in order to shave off a minute, the complexity of the pipeline increases dramatically (caching being a tricky example). So do y'all have any opinions on what makes a build slow for you?
- thinkingkong 7y agoI think the build / deploy times are more secondary. To me the more important part is the time to recover from an outage where a rollback is the fastest or best solution.
- pasxizeis 7y agoFor us, when assets had to be compiled, a production deploy would take 15-17 minutes. After mistry (when asset compilation time was shaved off), deployment takes ~5 mins.