-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins version 2.176.2
Windows Server 2019 Base
Unity 2017.4.26f1
Unity3D-plugin 1.3
Seems like the plugin doesn't work at all. It does not find the log file, regardless of where the log is placed.
Here is log output when using default location:
// Time Elapsed 00:00:10.32 Piping unity Editor.log from C:\Windows\system32\config\systemprofile\AppData\Local\Unity\Editor\Editor.log [Katanga] $ "C:\Program Files\Unity\Editor\Unity.exe" -quit -batchmode -nographics -executeMethod ReleaseBuild.Build -projectPath "C:\Program Files (x86)\Jenkins\workspace\Katanga\UnityScreenApp" WARNING: No change detected to Editor.log path: 'C:\Windows\system32\config\systemprofile\AppData\Local\Unity\Editor\Editor.log'. The unity3d plugin was probably unable to find it in its expected locations (see JENKINS-24265). Consider using the -logFile argument to force a known editor.log path or report the issue.
The default location (in systemprofile) is working for Unity, the log is created, is complete, and the build was a success. None of the info from the file is copied to the Jenkins output.
Similar output if I specify a different log file location using -logfile:
// Time Elapsed 00:00:09.95 Piping unity Editor.log from C:\Windows\system32\config\systemprofile\AppData\Local\Unity\Editor\Editor.log [Katanga] $ "C:\Program Files\Unity\Editor\Unity.exe" -quit -batchmode -nographics -executeMethod ReleaseBuild.Build -projectPath "C:\Program Files (x86)\Jenkins\workspace\Katanga\UnityScreenApp" -logfile "C:\Program Files (x86)\Jenkins\workspace\Katanga\unity_build.log"WARNING: No change detected to Editor.log path: 'C:\Windows\system32\config\systemprofile\AppData\Local\Unity\Editor\Editor.log'. The unity3d plugin was probably unable to find it in its expected locations (see JENKINS-24265). Consider using the -logFile argument to force a known editor.log path or report the issue.
It looks like even if I specify the log destination in the $WORKSPACE, that the plugin does not change it's location.
I've installed and tested this on two different servers, one Windows 2016, one Windows 2019. Both running on AWS.
I know the plugin has not been touched in quite a long time, but that doesn't matter if it is still working. Is it still working?
