Jenkins

Game builds are long, platform specific and easy to break. A build server runs them on a schedule or on every change, produces packages for each target, runs automated tests against them and reports what failed.

The server is one piece of a pipeline. Around it sit CI/CD as the wider subject, Docker for reproducible build environments, cloud services for the machines, Git for the source and a bug tracker for what the pipeline finds. Scripting is assumed, because a pipeline is scripts held together by the server.

Roles that ask for it are build, release and infrastructure positions, and QA engineering where the tests have to run without anybody starting them. The value of the work is measured in waiting time: how long after a commit a tester can play the change, and how often that package arrives broken.