| Challenge | Solution | |-----------|----------| | Git LFS quota on GitLab.com | Use git-lfs with lfs.fetchinclude to limit downloaded assets | | Unity license activation in CI | Use unityci/editor image with built-in activation via personal license file | | Long build times | Split builds into parallel jobs (Windows, Linux, WebGL) | | Flaky tests (random generation) | Set fixed seed for procedural generation in test mode |
There are several open-source clones of Crossy Road hosted on GitLab (and GitHub) that developers create to learn game development. crossyroadgitlab
CrossyRoadGitLab proves that a complete DevOps pipeline for a Unity arcade game is achievable with minimal infrastructure. GitLab CI/CD reduces manual build effort, catches regressions automatically, and provides instant playable builds via GitLab Pages. The project serves as a template for other indie developers seeking robust automation without paid CI services. | Challenge | Solution | |-----------|----------| | Git
Runners : Shared GitLab runners with Unity installed via Docker image unityci/editor:2021.3-windows-mono . The project serves as a template for other
While there is no singular formal "deep paper" titled Crossy Road GitLab
| Metric | Before CI/CD | With GitLab CI/CD | |--------|--------------|-------------------| | Build time (Windows) | ~8 min (manual) | ~4 min (cached) | | Test execution | 0 (manual only) | 45 sec automated | | Deployment to team | ZIP via email | GitLab Pages link | | Regression bugs | ~3 per release | ~0.5 per release |