Simple way to fetch logs

[sebas77]

The unity support is demanding some logs and I am having a hard time to understand how to fetch them from a github action. I need these logs

Unity Editor Logs
Windows: %LOCALAPPDATA%\Unity\Editor\Editor.log
macOS: ~/Library/Logs/Unity/Editor.log
Linux: ~/.config/unity3d/Editor.log
Licensing Client Logs
Windows: %LOCALAPPDATA%\Unity\Unity.Licensing.Client.log
macOS: ~/Library/Logs/Unity/Unity.Licensing.Client.log
Linux: ~/.config/unity3d/Unity/Unity.Licensing.Client.log
Licensing Audits
Windows: %LOCALAPPDATA%\Unity\Unity.Entitlements.Audit.log
macOS: ~/Library/Logs/Unity/Unity.Entitlements.Audit.log
Linux: ~/.config/unity3d/Unity/Unity.Entitlements.Audit.log
Services Configuration
Windows: %PROGRAMDATA%\Unity\config\services-config.json
macOS: /Library/Application Support/Unity/config/services-config.json
Linux: /usr/share/unity3d/config/services-config.json

chatgpt is not helping and I couldn't find it in the documentation, help?

this is a self-hosted runner, it would be useful to have a way to fetch the log out of the box. even -logFile is not clear to me, I suppose I can use a local absolute path tho?

[webbertakken]

We could probably make a flag that outputs those files from builder action, since we now known the exact locations of where they are supposed to be :)

[sebas77]

Ok thanks meanwhile if you know how I could get them (I am not a docker expert) I could do some experiments, but it's not as important as before as I don't need the logs anymore Best Regards, *Sebastiano Mandalà*

…

On Thu, Oct 2, 2025, 11:41 Webber Takken ***@***.***> wrote: *webbertakken* left a comment (game-ci/unity-builder#740) <#740 (comment)> We could probably make a flag that outputs those files from builder action, since we now known the exact locations of where they are supposed to be :) — Reply to this email directly, view it on GitHub <#740 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHGZY3ZX2SSYAP3P3LCT7T3VT6L3AVCNFSM6AAAAACIBUJ7QCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRQGQ2DOOBQGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>