Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct here to familiarize yourself with the rules and how to post constructively.

  2. Unity 2022.1 is now available as the latest Tech release.
    Dismiss Notice
  3. Improve your project's performance with our new guide on profiling in Unity.
    Dismiss Notice

CLI somewhat broken in 2.1.0

Discussion in 'Unity Hub' started by mcarriere, Aug 8, 2019.

  1. mcarriere


    Sep 14, 2012
    First off, this is awesome, thank you for moving in this direction. I imagine this will make our management with Jenkins easier down the road.

    A few issues I'd like to mention re: CLI

    1) On macOS (Mojave 10.14.5), there is some garbage output with the command:

    $ Builds > /Applications/Unity\\ Hub -- --headless help
    <CFData 0x7fc191c1a760 [0x7fff92e3c8e0]>{length = 6, capacity = 6, bytes = 0xf01898aeec7e}
    <CFData 0x7fc161d84300 [0x7fff92e3c8e0]>{length = 6, capacity = 6, bytes = 0xf01898aeec7e}

    2) The Hub is brought to the forefront with every invocation of a command. (This kinda defeats the headless bit.)

    3) The command itself does not follow common arg practices, the base prefix "-- --headless" is very odd.
    shadownicka likes this.
  2. AbrahamDUnity


    Unity Technologies

    Jun 28, 2017

    Thank you for the praise :D. Also, we are aware of these issues. We will definitely fix them in the coming releases. The weird output is a side effect that should be corrected by updating some of our dependencies. The Hub being brought to the front will be fixed but for now it is perhaps better to quit the Windowed Hub when using the command-line. Finally the "headless" argument was a shortcoming we had to ship with but the goal is to get rid of it.

    Thanks again for the feedback!
    shadownicka and mcarriere like this.