Jenkins: Unity batch mode build successful - Build folder empty





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I have a new Jenkins slave set up on which I call Unity CLI to build using my custom build method:



touch holo-build.log
if ! "$UNITY_APP" -projectPath "$WORKSPACE"
-buildTarget WindowsStoreApps
-executeMethod "$BUILD_METHOD"
-quit -batchmode -logFile holo-build.log
then
echo "Unity did not report a successful build, refer to the holo-build.log to get details"
exit 1
fi


This actually already works on a different slave. On the new one however, Unity quits with success exit code (0) - causing Jenkins to proceed normally, but actually never created the solution. The whole Build folder remains empty except for the logfile, which does also not report anything special, only compilation notes with warnings but without errors and the last logged line is "Exiting batchmode successfully"



What could be the issue here?










share|improve this question





























    0















    I have a new Jenkins slave set up on which I call Unity CLI to build using my custom build method:



    touch holo-build.log
    if ! "$UNITY_APP" -projectPath "$WORKSPACE"
    -buildTarget WindowsStoreApps
    -executeMethod "$BUILD_METHOD"
    -quit -batchmode -logFile holo-build.log
    then
    echo "Unity did not report a successful build, refer to the holo-build.log to get details"
    exit 1
    fi


    This actually already works on a different slave. On the new one however, Unity quits with success exit code (0) - causing Jenkins to proceed normally, but actually never created the solution. The whole Build folder remains empty except for the logfile, which does also not report anything special, only compilation notes with warnings but without errors and the last logged line is "Exiting batchmode successfully"



    What could be the issue here?










    share|improve this question

























      0












      0








      0








      I have a new Jenkins slave set up on which I call Unity CLI to build using my custom build method:



      touch holo-build.log
      if ! "$UNITY_APP" -projectPath "$WORKSPACE"
      -buildTarget WindowsStoreApps
      -executeMethod "$BUILD_METHOD"
      -quit -batchmode -logFile holo-build.log
      then
      echo "Unity did not report a successful build, refer to the holo-build.log to get details"
      exit 1
      fi


      This actually already works on a different slave. On the new one however, Unity quits with success exit code (0) - causing Jenkins to proceed normally, but actually never created the solution. The whole Build folder remains empty except for the logfile, which does also not report anything special, only compilation notes with warnings but without errors and the last logged line is "Exiting batchmode successfully"



      What could be the issue here?










      share|improve this question














      I have a new Jenkins slave set up on which I call Unity CLI to build using my custom build method:



      touch holo-build.log
      if ! "$UNITY_APP" -projectPath "$WORKSPACE"
      -buildTarget WindowsStoreApps
      -executeMethod "$BUILD_METHOD"
      -quit -batchmode -logFile holo-build.log
      then
      echo "Unity did not report a successful build, refer to the holo-build.log to get details"
      exit 1
      fi


      This actually already works on a different slave. On the new one however, Unity quits with success exit code (0) - causing Jenkins to proceed normally, but actually never created the solution. The whole Build folder remains empty except for the logfile, which does also not report anything special, only compilation notes with warnings but without errors and the last logged line is "Exiting batchmode successfully"



      What could be the issue here?







      unity3d jenkins command-line windows-store-apps hololens






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 3 at 15:12









      fridayfriday

      6111921




      6111921
























          1 Answer
          1






          active

          oldest

          votes


















          1














          Turns out Unity doesnt like to run outside a normal user. The jenkins service was set up to run under the system account which caused Unity to behave weirdly.



          After changing the service to run under a normal user account, everything started working fine.



          Note: there is also an interactive mode in the service properties when using the system account, which I thought might be enough, but failed as well.






          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025018%2fjenkins-unity-batch-mode-build-successful-build-folder-empty%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Turns out Unity doesnt like to run outside a normal user. The jenkins service was set up to run under the system account which caused Unity to behave weirdly.



            After changing the service to run under a normal user account, everything started working fine.



            Note: there is also an interactive mode in the service properties when using the system account, which I thought might be enough, but failed as well.






            share|improve this answer




























              1














              Turns out Unity doesnt like to run outside a normal user. The jenkins service was set up to run under the system account which caused Unity to behave weirdly.



              After changing the service to run under a normal user account, everything started working fine.



              Note: there is also an interactive mode in the service properties when using the system account, which I thought might be enough, but failed as well.






              share|improve this answer


























                1












                1








                1







                Turns out Unity doesnt like to run outside a normal user. The jenkins service was set up to run under the system account which caused Unity to behave weirdly.



                After changing the service to run under a normal user account, everything started working fine.



                Note: there is also an interactive mode in the service properties when using the system account, which I thought might be enough, but failed as well.






                share|improve this answer













                Turns out Unity doesnt like to run outside a normal user. The jenkins service was set up to run under the system account which caused Unity to behave weirdly.



                After changing the service to run under a normal user account, everything started working fine.



                Note: there is also an interactive mode in the service properties when using the system account, which I thought might be enough, but failed as well.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 3 at 15:18









                fridayfriday

                6111921




                6111921
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025018%2fjenkins-unity-batch-mode-build-successful-build-folder-empty%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                    SQL update select statement

                    'app-layout' is not a known element: how to share Component with different Modules