Search Unity

  1. Unity 2019.1 is now released.
    Dismiss Notice

Beta version supported is a few weeks old

Discussion in 'Unity Cloud Build' started by Huacanacha, Apr 9, 2019.

  1. Huacanacha

    Huacanacha

    Joined:
    Aug 16, 2013
    Posts:
    37
    Hi, we are using the 2019.1 beta for one branch of our project. We have cloud build setup to use the latest 2019.1 beta but it is building in a version or two behind. Currently it tries to build with b9 where b10 and now f01 are available. I even set the build job configuration to specifically use b10 but the build log says it's still using b9 (which is a bug). Due to some package manager updates the use of b9 is causing builds to fail.

    Is the "latest beta" stream in Cloud Build expected to largely keep up to date with new beta releases as they become available? Or is there typically going to be a delay in adding new versions? We can keep making manual builds if this is the case - which would be understandable given we are dealing with betas and not production releases.

    Thanks!
     
  2. ollieblanks

    ollieblanks

    Unity Technologies

    Joined:
    Aug 21, 2017
    Posts:
    148
    Hi @Huacanacha

    Thanks for reaching out.

    New versions do need to go through the Unity Cloud Build testing process before being enabled in the service, which means that there is usually a slight delay between release of the Unity version and when it becomes available on Cloud Build.

    The bug you are referring to, should now be resolved and b10 should be available for use. 2019.1.0f1 is currently in testing and will be available for use shortly.

    Hope that helps!
     
    Huacanacha likes this.
  3. Abruzzi

    Abruzzi

    Joined:
    Feb 6, 2015
    Posts:
    6
    Same problem! If I even specifically choose 2019.1.0b10 or 2019.1.0f1 in cloud build, it still use 2019.1.0b9
     
  4. Huacanacha

    Huacanacha

    Joined:
    Aug 16, 2013
    Posts:
    37
    Thanks! That approach is understandable. I'm still getting the non-requested version bug though.

    In config:
    Unity version Unity 2019.1.0f1

    In build log:
    36: + Detecting Unity installation ...
    37: + Building with Unity installed at /UNITY_PATH/Unity/Unity-2019_1_0b9/Unity.app/Contents/MacOS/Unity

    Is that because 0f1 isn't certified yet? And in that case why is it available to select in build config? Should I try with b10?

    For the "latest beta" option is the expected behaviour that it will use the most recent Cloud Build verified Unity version (which may not be the absolute latest), while we can still select more recent versions if we do so manually?
     
    Last edited: Apr 10, 2019
  5. Huacanacha

    Huacanacha

    Joined:
    Aug 16, 2013
    Posts:
    37
    With b10 specified it's still trying to use b9...

    40: + Building with Unity installed at /UNITY_PATH/Unity/Unity-2019_1_0b9/Unity.app/Contents/MacOS/Unity
     
  6. brettkercher

    brettkercher

    Unity Technologies

    Joined:
    Mar 19, 2018
    Posts:
    1
    This should be fixed now, let us know if you're still seeing this issue!
     
    Huacanacha likes this.
  7. Huacanacha

    Huacanacha

    Joined:
    Aug 16, 2013
    Posts:
    37
    Today it's working. Thanks!

    38: + Building with Unity installed at /UNITY_PATH/Unity/Unity-2019_1_0f1/Unity.app/Contents/MacOS/Unity