Back to search

How long do builds take to cook before you can actually test the fixes?

TL;DRBuilds take roughly five to six hours to cook, improved from eight to twelve, and most of that process happens outside the speakers' own view.

Jared HuckabyHost, Community Manager

That is a good question. Are we at five hours now? Based on the email, when they first say we're starting it, it's about five or six hours.

Ben LesnickDirector of Community Engagement, Online Strategy and Spaceships

It used to be more like eight to 12 hours, and the process has improved quite a bit while I've been here. I think it's about five hours.

Jared HuckabyHost, Community Manager

Most of that goes on in Austin, so we don't have a lot of great visibility into it, but they try to keep us in the loop by emails and stuff. I know that they are never-ending. Those guys, when they pass one build, they're on to the next build.

Ben LesnickDirector of Community Engagement, Online Strategy and Spaceships

And when a build fails, they feel it. Sometimes the build will be cooking and then something terrible will happen before it's done. And we see all that.

Jared HuckabyHost, Community Manager

I'm consistently impressed with the work those guys in Austin are doing to test these things. It's a thankless job.

Ben LesnickDirector of Community Engagement, Online Strategy and Spaceships

Austin and Germany. We don't see the Germany folks as much, but there's DevOps there now.

Reverse the Verse›December 4th, 2015·
Published on this date.4 Dec 2015