u3d | platform set of tools to interact with Unity3D from command | Automation library

u3d requires some environment variables set up to run correctly. In particular processing log files requires your locales to be set to a UTF-8 locale. In your shell profile add the following lines:. You can find your shell profile at ~/.bashrc, ~/.bash_profile or ~/.zshrc depending on your system.
Every Unity version has a build number in the form of a 12 characters hexadecimal (e.g. bf5cca3e2788). You might have noticed them: those build numbers are currently part of the download URLs that u3d available displays. Most of the time Unity users won't have to pay attention to build numbers. In a few scenarios, they become important. For example, sometimes Unity releases multiple builds with the same version but different build numbers, e.g. when releasing hot fixes. If you need a hotfix release, you might need to ensure that you are using it. Right now u3d has light support for build numbers. The build number can be found inside the Unity installation files and u3d will extract them and u3d list will display both the version and the build number. In the future u3d will have more features to help you managing installations of those special builds. Follow this request for enhancement for more information.
The standard Unity installer has some quirks:. Also for easing discoverability, it is recommended that you install your Unity versions in a similar area. For these reasons, u3d has standardized the installation paths of the Unity version it installs. u3d should be able to find the different unity installed under those locations. If the Unity installations are not in those locations, u3d might not find them automatically.
on Mac, it always installs Unity on /Applications/Unity. If you want to add a module to a particular version, you will have to move the unity you are trying to extend to that particular location
on Linux, most versions are installed as unity-editor-$version with version following the 'standard' numbering (except for some weird versions, see above). Unity lets you install the program in the directory of your choice
on Mac, versions are installed under /Applications/Unity_$version
on Linux, versions are installed under /opt/unity-editor-$version
on Windows, versions are installed under C:/Program Files/Unity_$version
u3d install accepts an argument --installation_path which can install unity and its additional components to the location you want. However, there is a pitfall to that: you need to tell u3d where to look for the versions you installed in custom location. Doing so is quite easy, you just have to set the U3D_EXTRA_PATHS, to a list of paths that you want u3d to look for versions. NOTE: The list of paths U3D_EXTRA_PATHS is formatted as your standard PATH, ie U3D_EXTRA_PATHS=/path/to/something:/another/path on Unix systems, and U3D_EXTRA_PATHS=C:\Path\To\Something;E:\Another\Path on Windows.
Here you have multiple options. For more information see also how to use u3d to install Unity on a CI server.
pass the password using U3D_PASSWORD environment variable
if on Mac, use the keychain option (you set it before hand on the machine, e.g. from the command line using u3d credentials add (use u3d credentials check to verify) and then use u3d install -k to activate the keychain while installing.
On MacOS and Linux:. Your usual package manager should be available to install it easily for you. On UNIX systems, we recommend you use RVM (Ruby Version Manager), which lets you manage several versions of Ruby. Installing Ruby on Windows is a bit more complicated than installing it on Linux or Mac. You have several options available: Bash on Ubuntu on Windows (see further note), Cygwin but we recommend you use the Ruby Installer for Windows. NOTE: We do not support Bash on Ubuntu on Windows. Most features of u3d will not work as intended on this platform and we therefore strongly advice you against using u3d on it.
On MacOS and Linux:
On Windows: