Jenkins and unity5.0.0f4 build step errors

Hi,

today i ran into a problem with our jenkins buildserver and the unity3d plugin for it it builds the .exe of the game correctly but it hangs at this error and never exits so our final build steps cannot complete theirselves.

Unloading 2 unused Assets to reduce memory usage. Loaded Objects now: 523.
Total: 2.699615 ms (FindLiveObjects: 0.131413 ms CreateObjectMapping: 0.026965 ms MarkObjects: 2.520755 ms  DeleteObjects: 0.017749 ms)


*** Completed 'Build.Player.WindowsStandaloneSupport' in 22 seconds (21570 ms)

Symbol file LoadedFromMemory doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
Symbol file C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll.mdb doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
Symbol file LoadedFromMemory doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
Symbol file C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll.mdb doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
Symbol file LoadedFromMemory doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll
Symbol file C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll.mdb doesn't match image C:\Program Files\Unity\Editor\Data\PlaybackEngines\webglsupport\UnityEditor.WebGL.Extensions.dll

I don’t know why unity us using webgl files for a win standalone build.

Found a workaround + found a possible linked bug with the plugin
https://issues.jenkins-ci.org/browse/JENKINS-27232

I also contacted the developer and we found a solution to ignore the logfile
but also using the -logfile “$WORKSPACE\unity3d_editor.log” ignores the error.

what arguments are you passing to unity?

-quit -batchmode -nographics -logFile “$WORKSPACE\bin\build.log” -buildWindowsPlayer “$WORKSPACE\bin$UPSTREAM_JOB_NAME.exe”

We use a parameterized build with a few variables for workspace and job names but this is the type of thing we are doing and it works fine.

I have run into issues like yours in the past for various reasons.

  1. are you missing any arguments? -quit -batchmode -nographics?
  2. what operating system are you using? Mac OSX has issues with graphics devices when running from command line if you dont supply the -nographics flag.
  3. was the previous jenkins job that ran in that workspace a webgl build? its possible that the editor didn’t wait for te buildtarget to update to PCStandalone.