Game Build Farm and Certification Board

Game Build Farm and Certification Board is a VibeControls concept for game studios that ship one game to several platforms at once. It puts last night's builds and each platform's certification progress on one board, so build engineers and producers can see before the morning standup what broke, on which machine, and whether the submission date still holds.

In a game studio, a patch can go out on PC, console, handheld and mobile, with the game servers updated alongside. Each target runs an overnight pipeline of compiling, content cooking, packaging and smoke testing on a shared farm of build machines. When a cook fails, the cause is often mundane, such as a machine that ran out of disk, yet it surfaces only after someone digs through logs. Certification requirements and the bugs that block them are tracked elsewhere, so build and certification status are rarely read together as the submission window closes.

The illustration shows a sample season patch opened from the Scheduler, with the nightly run's time range, the number of build machines and an amber countdown to the close of the submission window. A Build stages by platform matrix gives each platform and the game servers a row of Compile, Content cook, Package and Smoke test results, smoke tests shown as passed against total, then the build machine, the run duration and that machine's free disk. In the sample, the console row is highlighted: its content cook failed, packaging was skipped, smoke tests did not run, and its machine has almost no disk left. A card beneath explains that a write failed because the output volume was full, with Open build log and a button to rerun the stage on a different machine. A Rerun failed stages button sits at the top of the board.

Beside the matrix, Certification by platform totals the checklist items met and the blocking bugs, which are linked from the matching PlanMagnet release. The console card lists two linked bugs and reads blocked, the handheld has one open item and one fix to verify, mobile has a store review checklist still open, PC needs no certification, and the game servers, which are deployed rather than submitted, read deploy ready. The board is designed to receive those certification-blocking bugs from the PlanMagnet release where they are planned, and to post build and checklist status back to that release's checklist, so producers see the same answer in both places.

The board sits under the Scheduler in the Automation section, next to Actions, Decks and the Calendar, so the design treats the nightly run as one more scheduled job, with its failed stages rerun from the board itself.