Unity Hub CLI feedback & features request

Hi! We extensively use our infrastructure based on Gitlab CI to build binaries for target platforms with Unity. For this, we have a lot of build machines: VMs and Mac minis. To manage the environment on those machines we are planning to use Puppet. To manage Unity installations we need an instrument with CLI.

I was happy to know, that Unity Hub has a CLI, but it’s so limited that it’s hard to make it work.

What do we need in general:

  • Get a list of installed editors;
  • Get a list of all available editors (with all information needed for install action);
  • Get a list of installed modules for the given installed editor version;
  • Instal and uninstall specific versions of an editor (including Intel / Apple Silicon versions for macOS);
  • Instal and uninstall specific modules for the given installed editor version;
  • Сheck the activation of the given licence key, and activate it if needed only by CLI (without human);
  • Perform all actions above without starting an application.

Which critical makes Hub unusable now:

  • It isn’t possible to install Apple Silicon editors;

  • It isn’t possible to uninstall editors;

  • It isn’t possible to get a list of installed modules for a given editor;

  • It isn’t possible to uninstall modules for a given editor;

  • It isn’t possible to activate a builder licence without human interaction;

  • You need to provide a changeset parameter to install an Editor;

  • Even with --headless flag, it starts Hub applications, which slows the execution of check commands.

Currently, we have a solution which does most of that stuff - the u3d Ruby Gem, but it has delayed support and doesn’t work well with Hub.

I will be very thankful for more attention to the CLI part, and ready to provide even deeper feedback and use cases.

hell it doesn’t even give you the ability to get something as basic as the version

Until a few days ago this issue was marked as by design…

This has finally been corrected in 3.4.0.

It has only taken them a few years to fix such a big problem…

Unfortunately. This requires minimum time (as I see it). Currently, it’s so hard to automate the M1 install. Even if you download and install from the archive, installing modules is a mess.

Yeah I was told the same thing when I opened this bug almost 2 years ago… It’s their way of closing tickets without actually fixing anything.

It isn’t possible to install Apple Silicon editors;
Fix for this point available in this thread Unity Hub CLI on m1 mac

Hi, thanks for sharing. Unfortunately for us, it’s unusable due to: