Search Unity

  1. Unity 2019.2 is now released.
    Dismiss Notice

OSX CI machine - License Activation w. batchmode (not as root)

Discussion in 'Editor & General Support' started by buildmonster3, Jul 15, 2019.

  1. buildmonster3

    buildmonster3

    Joined:
    Jul 14, 2019
    Posts:
    2
    Hi,
    We are installing Unity on CI machine (OSX High Sierra) by copying a dmg (eg. Unity_2017.4.16.dmg), mounting it and copying the files to /Application/Unity_{version}, this is all done using a non root user let's call it foo (foo is an admin user).

    We are trying to activate unity license using unity batchmode, but, the first run is asking for foo's password to run some wizard that creates required directories such as the license directory (when providing foo's password or running the command as root (w. sudo), it creates the license directory successfully in: /Library/Application../Unity/

    This is the command we are running:
    sudo /Applications/Unity_2017.4.16/Unity.app/Contents/MacOS/Unity -quit -batchmode -serial {{ unity.serial }} -username '{{ unity.email }}' -password '{{ unity.password }}' -logfile -

    We tried both with and without sudo.

    We see that the license is being activated successfully (and the license ulf file is created), but when we open Unity, we are being asked to sign in.

    When we open unity as root (using sudo), Unity is signed in with our user.

    Our pipelines are using foo as the running user.

    Needless to say, when we sign in through the UI, Unity is signed even when user foo is opening it.

    We are aiming for a fully automated configuration management for our CI servers.

    What are we missing?
    What is the right way to go?
    Anyone worked around this?
     
  2. buildmonster3

    buildmonster3

    Joined:
    Jul 14, 2019
    Posts:
    2
    I'm not sure if bumping is a thing.. can someone help us please