CI/CD Pipelines

Overview

Remangu CI/CD Pipelines provide automated build farms purpose-built for game development and real-time content creation workflows. The platform integrates natively with Perforce Helix Core, enabling changelist-driven build triggers that automatically compile, cook, package, and test Unreal Engine and Unity projects without manual intervention.

Build infrastructure scales horizontally using ephemeral compute instances that spin up for each job and terminate on completion. Studios avoid the capital expense and maintenance burden of on-premises build hardware while achieving faster iteration cycles through parallelized build stages. Completed artifacts flow into managed repositories with versioning, retention policies, and one-click deployment to staging and production environments.

Key Features

• Perforce Integration — Build pipelines trigger directly from Perforce changelist submissions, branch operations, or scheduled intervals. Source syncs use Perforce edge servers for maximum throughput, and build metadata is written back to Perforce labels for full traceability.
• Unreal/Unity Build Support — Pre-configured build agents include Unreal Engine 5 and Unity 6 toolchains with all required SDKs, platform compilers, and signing certificates. Custom engine forks and plugin dependencies are supported through versioned agent images.
• Parallel Builds — Large projects are decomposed into independent build stages—shader compilation, asset cooking, code compilation, lighting builds—that execute in parallel across multiple agents. Total build times drop by 60-80% compared to sequential execution.
• Automated Testing — Integrate unit tests, functional tests, and automated playtests into the pipeline. Test results gate promotion to downstream stages, ensuring that only validated builds reach QA or staging environments.
• Artifact Management — Build outputs are stored in a managed artifact repository with semantic versioning, retention policies, and access controls. Teams browse, compare, and deploy any historical build through the Remangu console or CLI.

Technical Specifications

Specification	Detail
Supported Engines	Unreal Engine 4/5, Unity 2022/6
Build Scaling	Auto-scaling ephemeral agents
Source Integration	Perforce Helix Core (native), Git (supported)
Parallelism	Multi-stage, multi-agent parallel execution
Artifact Storage	Versioned repository with configurable retention
Deployment Targets	Staging, Production, Playtest environments
Platforms	Windows, Linux, macOS, console SDK builds

How It Works

1. Define Pipelines — Authors configure build pipelines as code using YAML definitions or the visual pipeline editor. Each pipeline specifies source triggers, build stages, test gates, and deployment targets.
2. Trigger — A Perforce changelist submission or scheduled event initiates the pipeline. The orchestrator provisions the required number of build agents from the auto-scaling pool and begins source synchronization.
3. Build & Test — Agents execute build stages in parallel where dependency graphs allow. Compilation, cooking, packaging, and testing run as isolated steps with per-stage logging and failure isolation. Failed stages halt downstream promotion.
4. Deliver — Successful builds produce versioned artifacts deposited in the managed repository. One-click or automated deployment pushes artifacts to staging for QA review, then to production or playtest distribution endpoints upon approval.