feat(cli): collectUnityLogs + streamUnityLogs flags (refs unity-builder#740)#48
Conversation
Mirrors the Orchestrator's Unity diagnostic log collection feature on the standalone CLI. After a Docker build the CLI gathers Editor.log, Unity.Licensing.Client.log, Unity.Entitlements.Audit.log, services-config.json, build report, bee_backend.log, ProjectVersion.txt and Packages/manifest.json into <workspace>/Logs/UnityDiagnostics/ along with a manifest.json. Live tailing of the Unity -logFile output is also wired in. The orchestrator package owns the canonical, multi-platform path registry (UnityLogCollectorService) — the CLI keeps a slim subset for users running game-ci build directly. The orchestrate flow inherits the full implementation via the @game-ci/orchestrator plugin. Flags: --collectUnityLogs --collectUnityLogsOnSuccess --unityLogCategories --unityLogsIncludeSensitive --unityLogsOutputDir --streamUnityLogs --streamUnityLogPaths Refs: game-ci/unity-builder#740 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Adds a discoverable verb-first surface for Unity diagnostic logs: game-ci logs collect [--unityLogCategories ...] [--unityLogsOutputDir ...] game-ci logs tail [--streamUnityLogPaths ...] game-ci logs pull # stub — points at orchestrator roadmap issue game-ci logs fetch # stub — points at orchestrator roadmap issue Replaces the awkward `game-ci orchestrate --providerStrategy local --collectUnityLogs ...` recipe with a one-liner. `logs collect` runs the same UnityLogs collector against the local host, so users can SSH into a self-hosted runner after a failing job and grab the Unity-support bundle without editing the workflow. `logs tail` runs UnityLogs.streamFiles until Ctrl+C and is the standalone counterpart to streamUnityLogs=true on a running build. `logs pull` and `logs fetch` are reserved for the upcoming remote-provider exec and retroactive-fetch follow-ups; for now they print actionable messages pointing users to the existing path. Wired into the unity plugin's command dispatcher. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Summary
Companion to game-ci/orchestrator#23 — surfaces the same Unity diagnostic log collection feature on the standalone
game-ciCLI.After a Docker build, the CLI gathers
Editor.log,Unity.Licensing.Client.log,Unity.Entitlements.Audit.log,services-config.json, build report,bee_backend.log,ProjectVersion.txt, andPackages/manifest.jsoninto<workspace>/Logs/UnityDiagnostics/along with amanifest.json. Live tailing of the Unity-logFileoutput is also wired in.Notes
UnityLogCollectorServicewith ~17 categories). The CLI keeps a slim subset for users runninggame-ci builddirectly. Theorchestrateflow inherits the full implementation via the@game-ci/orchestratorplugin.New flags
```
--collectUnityLogs
--collectUnityLogsOnSuccess
--unityLogCategories
--unityLogsIncludeSensitive
--unityLogsOutputDir
--streamUnityLogs
--streamUnityLogPaths
```
Test plan
bun buildcleancommand-optionstests passgame-ci build --targetPlatform StandaloneLinux64 --collectUnityLogsagainst a self-hosted Linux runner; confirmLogs/UnityDiagnostics/manifest.jsonappears🤖 Generated with Claude Code