Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: unity3d-plugin
-
Labels:None
-
Environment:Master running on cloud-based Linux machine
Dumb slave running on Windows machine via Java Web Start
-
Similar Issues:
Description
The master is being used just to trigger builds which are then run on slaves.
The slave is configured as a dumb slave.
I add a Unity3D installation on the master named UNITY_WINDOWS (Manage Jenkins -> Configure System -> Unity3d) but get an error if I enter the windows path in the installation directory so leave blank.
I can then go to the slave configuration (Manage Jenkins -> Manage Nodes -> Select XXX -> Configure -> Tool Locations) and see (Unity3d) UNITY_WINDOWS in the drop down. I can enter the path here (C:\Program Files (x86)\Unity\Editor\Unity.exe) but this is not used when building.
In a free-style job I can also select UNITY_WINDOWS in the Unity3d installation name.
On running, the following error message is displayed:
FATAL: Executable not found UNITY_WINDOWS
Build step 'Invoke Unity3d Editor' marked build as failure
Attachments
Activity
Code changed in jenkins
User: Jerome Lacoste
Path:
src/main/resources/org/jenkinsci/plugins/unity3d/Unity3dInstallation/help-home.html
http://jenkins-ci.org/commit/unity3d-plugin/453756dc576bd0ddc4315ec5f6c2cf34d8fd555e
Log:
[FIXED JENKINS-20349] improved Tool installation Unity3d home field documentation
Compare: https://github.com/jenkinsci/unity3d-plugin/compare/da01defa5c99...453756dc576b
Code changed in jenkins
User: Jerome Lacoste
Path:
src/main/java/org/jenkinsci/plugins/unity3d/Unity3dBuilder.java
src/main/java/org/jenkinsci/plugins/unity3d/Unity3dInstallation.java
src/main/resources/org/jenkinsci/plugins/unity3d/Messages.properties
http://jenkins-ci.org/commit/unity3d-plugin/4d945112aaf5384d98a251763a018c956c002025
Log:
[FIXED JENKINS-20349] improved configuration error detection for Unity3d installation directory path
I will close this issue:
- the configuration on the master is now optional
- the home field for the tool installation directory is now documented
- both the configuration in the master and the retrieval of the installation path at job execution time fail with relevant contextual information (print out the installation path and expected path of the executable)
I hope this is enough!
lacostej
added a comment - I will close this issue:
the configuration on the master is now optional
the home field for the tool installation directory is now documented
both the configuration in the master and the retrieval of the installation path at job execution time fail with relevant contextual information (print out the installation path and expected path of the executable)
I hope this is enough! 
I agree we need to update the documentation.
Anyone willing to contribute a patch ?