Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22315

Jenkins stalls building project, works fine outside of jenkins

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The jenkins build runner fails to complete when building my project under windows 8.1

      It checks the project out from bitbucket fine, and runs fine until it gets to the 'used assets' list, at which point it just hangs and never completes.

      Running the exact same parameters from the command line executes fine. The editor script that I'm executing also works fine when run from within the editor.

      Will see if I can get it to reproduce with an example project...

        Attachments

          Activity

          Hide
          lacostej lacostej added a comment -

          Mike,

          I set up a Windows 8.1 build machine this morning (using the 1.532.2 stable version), and I am able to start the build without problem. With either unity3d-plugin 0.5 or 0.6 and Unity3d 4.3.3f1

          I suggest you look at the troubleshooting section:
          https://wiki.jenkins-ci.org/display/JENKINS/Unity3dBuilder+Plugin#Unity3dBuilderPlugin-Troubleshootingfailures

          Show
          lacostej lacostej added a comment - Mike, I set up a Windows 8.1 build machine this morning (using the 1.532.2 stable version), and I am able to start the build without problem. With either unity3d-plugin 0.5 or 0.6 and Unity3d 4.3.3f1 I suggest you look at the troubleshooting section: https://wiki.jenkins-ci.org/display/JENKINS/Unity3dBuilder+Plugin#Unity3dBuilderPlugin-Troubleshootingfailures
          Hide
          lacostej lacostej added a comment -

          Mike, any feedback on this ?

          Show
          lacostej lacostej added a comment - Mike, any feedback on this ?
          Hide
          gekido mike wuetherick added a comment -

          Hey,

          Haven't had time to look into it much since, but I do know that the same project runs fine with the command line parameters launched as a batch script (from jenkins) instead of using the build runner directly.

          so what I've done is created a platform-specific batch file and am launching that from jenkins instead of using the Unity plugin. I have a new project to hook up today so I'll see if I can spend some time trying to get it to work with the Unity plugin again this weekend.

          Show
          gekido mike wuetherick added a comment - Hey, Haven't had time to look into it much since, but I do know that the same project runs fine with the command line parameters launched as a batch script (from jenkins) instead of using the build runner directly. so what I've done is created a platform-specific batch file and am launching that from jenkins instead of using the Unity plugin. I have a new project to hook up today so I'll see if I can spend some time trying to get it to work with the Unity plugin again this weekend.
          Hide
          grofie Fiete Groth added a comment -

          I ran into the same problem, after days of research and failure, I finally found the solution:

          You simply need to change the user the jenkins service is using.

          By default, Jenkins uses the default user, which did not have enough access rights. Now it is all working fine (with Windows 8.1, Unity 4.3.4 and the Unity plugin v0.6).

          Show
          grofie Fiete Groth added a comment - I ran into the same problem, after days of research and failure, I finally found the solution: You simply need to change the user the jenkins service is using. By default, Jenkins uses the default user, which did not have enough access rights. Now it is all working fine (with Windows 8.1, Unity 4.3.4 and the Unity plugin v0.6).
          Hide
          simon_yu simon yu added a comment -

          I love u ! Fiete! You saved me! This problem bothered me 3 days! I tried all kinds of means , remove and install several versions of ADT, JDK, Unity, Jenkins, and just before I reinstall my windows, I found this, your comment, you are really a good good man!

          Show
          simon_yu simon yu added a comment - I love u ! Fiete! You saved me! This problem bothered me 3 days! I tried all kinds of means , remove and install several versions of ADT, JDK, Unity, Jenkins, and just before I reinstall my windows, I found this, your comment, you are really a good good man!
          Hide
          lacostej lacostej added a comment -

          Given that building was working when running from the command line, I don't see why changing permissions would have affected this.

          I have another potential explanation: JENKINS-27710 (fixed today) was causing jenkins to hang if the plugin wasn't able to find the Editor.log.

          Changing user might just have made it easier for jenkins to find the Editor.log.

          If anyone used the work-around identified in this issue, please try with version 0.7 and see if the job still hangs.

          In the mean time, I'll close this issue.

          Show
          lacostej lacostej added a comment - Given that building was working when running from the command line, I don't see why changing permissions would have affected this. I have another potential explanation: JENKINS-27710 (fixed today) was causing jenkins to hang if the plugin wasn't able to find the Editor.log. Changing user might just have made it easier for jenkins to find the Editor.log. If anyone used the work-around identified in this issue, please try with version 0.7 and see if the job still hangs. In the mean time, I'll close this issue.
          Hide
          lacostej lacostej added a comment -

          Most probaby a dupe of JENKINS-27710

          Show
          lacostej lacostej added a comment - Most probaby a dupe of JENKINS-27710

            People

            Assignee:
            lacostej lacostej
            Reporter:
            gekido mike wuetherick
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: