ci-cd-automation
Continuous integration and deployment pipelines, automated testing, build automation, and team workflows for game development.
What this skill does
# CI/CD Automation
## Pipeline Architecture
```
┌─────────────────────────────────────────────────────────────┐
│ CI/CD PIPELINE STAGES │
├─────────────────────────────────────────────────────────────┤
│ TRIGGER: [Push] [PR] [Tag] [Schedule] [Manual] │
│ ↓ │
│ VALIDATE (< 5 min): │
│ Lint → Compile Check → Asset Validation │
│ ↓ │
│ TEST (10-30 min): │
│ Unit Tests → Integration → PlayMode Tests │
│ ↓ │
│ BUILD (Parallel): │
│ [Windows] [Linux] [macOS] [WebGL] [Android] [iOS] │
│ ↓ │
│ DEPLOY: │
│ [Dev auto] → [Staging gate] → [Prod approval] │
└─────────────────────────────────────────────────────────────┘
```
## GitHub Actions for Unity
```yaml
# ✅ Production-Ready: Unity CI/CD Pipeline
name: Unity Build Pipeline
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
workflow_dispatch:
inputs:
buildType:
description: 'Build type'
required: true
default: 'development'
type: choice
options:
- development
- release
env:
UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
lfs: true
- uses: actions/cache@v3
with:
path: Library
key: Library-${{ hashFiles('Assets/**', 'Packages/**', 'ProjectSettings/**') }}
restore-keys: Library-
- uses: game-ci/unity-test-runner@v4
with:
testMode: all
artifactsPath: test-results
checkName: Test Results
- uses: actions/upload-artifact@v3
if: always()
with:
name: Test Results
path: test-results
build:
needs: test
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
targetPlatform:
- StandaloneWindows64
- StandaloneLinux64
- WebGL
steps:
- uses: actions/checkout@v4
with:
lfs: true
- uses: actions/cache@v3
with:
path: Library
key: Library-${{ matrix.targetPlatform }}-${{ hashFiles('Assets/**', 'Packages/**') }}
- uses: game-ci/unity-builder@v4
with:
targetPlatform: ${{ matrix.targetPlatform }}
versioning: Semantic
buildMethod: BuildScript.PerformBuild
- uses: actions/upload-artifact@v3
with:
name: Build-${{ matrix.targetPlatform }}
path: build/${{ matrix.targetPlatform }}
retention-days: 14
deploy-staging:
needs: build
if: github.ref == 'refs/heads/develop'
runs-on: ubuntu-latest
environment: staging
steps:
- uses: actions/download-artifact@v3
with:
name: Build-WebGL
path: build/
- name: Deploy to Staging
run: |
# Deploy to staging server
aws s3 sync build/ s3://game-staging-bucket/
```
## Unreal Engine Pipeline
```yaml
# ✅ Production-Ready: Unreal CI/CD
name: Unreal Build Pipeline
on:
push:
branches: [main]
jobs:
build:
runs-on: [self-hosted, unreal]
steps:
- uses: actions/checkout@v4
with:
lfs: true
- name: Build Development
run: |
& "$env:UE_ROOT/Engine/Build/BatchFiles/RunUAT.bat" `
BuildCookRun `
-project="${{ github.workspace }}/MyGame.uproject" `
-platform=Win64 `
-clientconfig=Development `
-build -cook -stage -pak -archive `
-archivedirectory="${{ github.workspace }}/Build"
- uses: actions/upload-artifact@v3
with:
name: UnrealBuild-Win64
path: Build/
```
## Build Optimization
```
BUILD TIME OPTIMIZATION:
┌─────────────────────────────────────────────────────────────┐
│ STRATEGY │ TIME SAVINGS │ EFFORT │
├────────────────────────┼──────────────┼───────────────────┤
│ Library caching │ 30-50% │ Low │
│ Parallel builds │ 40-60% │ Low │
│ Self-hosted runners │ 20-40% │ Medium │
│ Incremental builds │ 50-80% │ Medium │
│ Asset bundles split │ 30-50% │ High │
└─────────────────────────────────────────────────────────────┘
```
## Automated Testing
```csharp
// ✅ Production-Ready: PlayMode Test
[TestFixture]
public class PlayerMovementTests
{
private GameObject _player;
private PlayerController _controller;
[UnitySetUp]
public IEnumerator SetUp()
{
var prefab = Resources.Load<GameObject>("Prefabs/Player");
_player = Object.Instantiate(prefab);
_controller = _player.GetComponent<PlayerController>();
yield return null;
}
[UnityTest]
public IEnumerator Player_MovesForward_WhenInputApplied()
{
var startPos = _player.transform.position;
_controller.SetInput(Vector2.up);
yield return new WaitForSeconds(0.5f);
Assert.Greater(_player.transform.position.z, startPos.z);
}
[UnityTearDown]
public IEnumerator TearDown()
{
Object.Destroy(_player);
yield return null;
}
}
```
## 🔧 Troubleshooting
```
┌─────────────────────────────────────────────────────────────┐
│ PROBLEM: Build times too long (>30 min) │
├─────────────────────────────────────────────────────────────┤
│ SOLUTIONS: │
│ → Enable Library folder caching │
│ → Use self-hosted runners with SSDs │
│ → Parallelize platform builds │
│ → Split large asset bundles │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ PROBLEM: Flaky tests causing failures │
├─────────────────────────────────────────────────────────────┤
│ SOLUTIONS: │
│ → Use test timeouts │
│ → Isolate tests properly │
│ → Add retry logic for network tests │
│ → Quarantine unstable tests │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ PROBLEM: Cache not restoring correctly │
├─────────────────────────────────────────────────────────────┤
│ SOLUTIONS: │
│ → Check cache key hash inputs │
│ → Verify cache path is correct │
│ → Use restore-keys for partial matches │
│ → Check cache size limits │
└─────────────────────────────────────────────────────────────┘
```
## Deployment Strategies
| Strategy | Rollback Time | Risk | Best For |
|----------|---------------|------|----------|
| Blue-Green | Instant | Low | Web builds |
| Canary | Minutes | Low | Mobile apps |
| Rolling | Minutes | Medium | Game servers |
| Big Bang | Hours | High | Console releases |
---
**Use this skill**: When setting up build pipelines, automating testing, or improving team workflows.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.