Skip to content

Add way to archive old build logs #1

@trigger-segfault

Description

@trigger-segfault

Right now, Unity purges editor logs (presumably) every time you open the editor. You only get the current log and previous log, so after two opens, you've lost all previous build log history. If you're like me, then builds happen infrequently between the constant refactoring, so it's common to have no previous build logs to scan.

Build logs could either be exported to an asset, a JSON file, or some other method. Persistence between all editors is probably for the best, since the log is for all editors, in which case, exporting to an editor pref could work, but that seems terrible with how large the build logs are in text format.

If an asset is chosen, then a second script file will need to be added, which is undesirable for this tool's plug-and-play design.

Additionally, to avoid archiving the same build logs twice, the GUIDs attached to each build (basically the whole bundle name) could probably be used as a unique identifier.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions