-
-
Notifications
You must be signed in to change notification settings - Fork 51
Description
Unity Tools for Azure DevOps - Bug Report
Describe the bug
When running a UnityCmdTask for some Pipelines I find that the log file is never created. After some investigation I found that the issue is that the Logs directory does not exist and is never created inside the temp directory for these tasks. If I manually create the Logs 'folder' at the correct time (before the Unity task but within the same job) it will create the log file as expected.
The pipeline that it works on is 6000.0.34f1
The pipeline that it doesn't create the Logs directory and therefore the logfile is 2018.4.18f1
Perhaps the -logFile arg for Unity will not auto-create missing sub-directories on specific (older) versions of Unity?
To Reproduce
Run UnityCmdTask with any args and check that the output variable log file path is valid by publishing an artifact, seems inconsistent - perhaps linked to editor version. Failed on 2018.4.18f1. Unsure why the Logs folder exists sometimes and not others.
Expected behavior
The output variable for the UnityCmdTask should point to a valid log file.
Actual behavior
The output variable for the UnityCmdTask points to a file that does not exist.
Screenshots
NA
Your Setup
Agent Type
- Hosted
- Self Hosted
Build Targets
- Windows
- Android
- iOS
- macOS
- Other (please specifiy)
Unity Version
2018.4.18f1