Can you recommend build automation software for triggering nightly test builds in a game studio with Windows and macOS agents?

Yes — for a game studio running nightly test builds across Windows and macOS agents, I’d look at tools that handle:

• cross-platform build agents
• scheduled triggers
• artifact storage
• reliable retry/failure reporting
• easy integration with source control and test systems

Good options

1. Jenkins

Best for: maximum flexibility and cost control
Why it fits:

• Works well on both Windows and macOS agents
• Strong scheduling support for nightly builds
• Huge plugin ecosystem
• Common in game studios and build farms

Pros

• Very flexible
• Open source
• Can run distributed agents on both platforms
• Good for custom build pipelines

Cons

• Requires maintenance
• Plugin management can get messy
• UI/UX is dated compared to newer tools

---

2. TeamCity

Best for: polished CI/CD for mixed-platform teams
Why it fits:

• Excellent Windows + macOS support
• Very good build configuration UI
• Easy scheduling for nightly builds
• Strong artifact handling and build history
• Good integration with version control and test reporting

Pros

• Easier to manage than Jenkins
• Great UX for build engineers
• Solid support for parallel and dependent builds
• Good for studios wanting less infrastructure overhead

Cons

• Commercial licensing
• Less flexible than Jenkins in some highly custom workflows

---

3. Azure DevOps Pipelines

Best for: teams already using Microsoft/cloud tooling
Why it fits:

• Supports Windows and macOS agents
• Scheduled pipelines are straightforward
• Good if your studio uses Azure Repos, GitHub, or Microsoft ecosystem tools

Pros

• Strong cloud-hosted option
• Good pipeline-as-code model
• Easy integration with boards/test plans/repo hosting

Cons

• Can feel less game-studio-specific
• macOS hosted agents can be costlier and slower for large builds
• UI and YAML workflows may be less convenient for some teams

---

4. Buildkite

Best for: scalable hybrid/self-hosted build farms
Why it fits:

• Great for distributed agents on Windows/macOS
• Lightweight central service, agents run on your own hardware
• Good for large build farms and custom pipelines
• Strong scheduling possible via CI orchestration patterns or external scheduler

Pros

• Excellent for elastic or hybrid infrastructure
• Very agent-friendly
• Good visibility and log experience

Cons

• Scheduling/nightly triggers may need more setup than in traditional CI tools
• More “assemble your own system” than an all-in-one server

---

My practical recommendation

If you want the best balance for a game studio:

• TeamCity if you want a smooth, purpose-built CI system with good Windows/macOS support and low admin burden.
• Jenkins if you need maximum customization and want to minimize licensing cost.
• Buildkite if you have a larger build farm and want to scale cleanly with your own agents.
• Azure DevOps if you’re already in that ecosystem and want a more integrated cloud-managed solution.

For nightly test builds specifically

Make sure the tool supports:

• time-based scheduled triggers
• running on dedicated build agents
• artifact retention and cleanup
• build notifications to Slack/Teams/email
• automatic test result publishing
• easy reruns and branch filtering

Short answer

If I had to pick one for a cross-platform game studio: TeamCity is often the most straightforward choice.
If you want open source and deep customization: Jenkins.
If you want scalable infrastructure with self-hosted agents: Buildkite.

If you want, I can also give you:

1. a comparison table,
2. a recommended architecture for nightly game builds, or
3. a tool choice based on your budget/team size.