Search Unity

Inconsistent package deployment by Unity

Discussion in 'Package Manager' started by snacktime, Sep 3, 2019.

  1. snacktime

    snacktime

    Joined:
    Apr 15, 2013
    Posts:
    3,356
    Not really sure the best place to put this since it spans multiple teams, although where I've noticed it most is with preview packages.

    Unity teams are not consistent about which repo's they push to. So that everything that is on production is not always on staging. Where some teams just push directly to production skipping staging.

    This creates significant pain. We can't use staging because some packages never land there. If we use production we then can't get the latest version. Only way to resolve it is just use a separate project to get what we need and then install the source in our main project.
     
    snacktime, Sep 3, 2019
    #1

  2. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    756
    Hi @snacktime ,

    The staging registry was decommissioned a couple of weeks ago. Having the staging registry public was a temporary solution until we properly set our internal workflows and infrastructure. This is now the case. We are keeping the registry around as a read-only registry to not break the projects of a few people who were mislead to using it. There won't be any new packages pushed there. Please use the *production* registry from now on.

    Regards,

    Pascal
     
    okcompute_unity, Sep 4, 2019
    #2
    Mauri likes this.

  3. snacktime

    snacktime

    Joined:
    Apr 15, 2013
    Posts:
    3,356
    Thanks very good to know, it all makes sense now.
     
    snacktime, Sep 4, 2019
    #3