Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: unity3d-plugin
-
Labels:None
-
Similar Issues:
Description
If editor.log is not searched for in the right place, e.g. JENKINS-24265 or similar, the plugin hangs as we do not close properly the output.
Attachments
Issue Links
- is related to
-
JENKINS-24265 Wrong auto-detected editor.log PATH on system user on Windows
-
- Resolved
-
-
JENKINS-27232 Unity 5.0.0f4 can't build
-
- Closed
-
Code changed in jenkins
User: Jerome Lacoste
Path:
src/main/java/org/jenkinsci/plugins/unity3d/io/PipeFileAfterModificationAction.java
http://jenkins-ci.org/commit/unity3d-plugin/b1d790c61a852b1006c280a1eaaa83234a288642
Log:
JENKINS-27710: close the output also if file modification was interrupted. We also output some warning to the job console, to help troubleshooting a bit and propose a work-around