Search Unity

  1. We are migrating the Unity Forums to Unity Discussions. On July 12, the Unity Forums will become read-only. On July 15, Unity Discussions will become read-only until July 18, when the new design and the migrated forum contents will go live. Read our full announcement for more information and let us know if you have any questions.

Feedback Promote a Release and preserve Badges

Discussion in 'Unity Cloud Content Delivery' started by Peter77, Sep 27, 2021.

  1. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,650
    I expected when I promote a
    Release
    that the
    Badges
    from the Release stay intact (except latest), but they're lost.

    Is the behavior that Badges are being lost in the Promote process on purpose?

    Why do I want to keep the Badges? Our game uses Badges to connect to a particular Release. We use the build version as Badge, e.g. Badge
    1_1_3
    serves content for build version
    1.1.3
    .

    Our build server syncs content to the
    Staging
    bucket and then assigns a Badge for this particular Build. When we then later promote the Release from
    Staging
    to
    Live
    , also via a build server job, we need the same Badges for the Build to connect to the correct content.

    If you don't want to change the existing Promote behavior in UCD, perhaps you can add an option that allows to specify something like
    --preserve-badges
    when promoting a Release.

    With the current behavior I have write code that:
    1. fetches Releases from the Staging bucket
    2. extracts the Badges from the release i want to promote
    3. promote Release to Live
    4. fetch releases from Live
    5. extract release_id from promoted release
    6. add Badges back to the promoted Release in Live using the extracted badges and release_id.
     
    Last edited: Sep 27, 2021
  2. darashayda

    darashayda

    Joined:
    Jun 27, 2020
    Posts:
    443
    Hello and thank you for this comment. You were reading my mind.

    We decided not to count on Unity for our version management for number of reasons.

    Our decision is to maintain our own versioning system at the expense of making number of redundant buckets and running our own versioning systems.

    Reason being is Unity can swing any which way with their functionality, like most US firms they do not commit to any particular software feature. Moreover as in the case of their Plastic SCM the bug fixes are rare!

    And it is also not their job, at some point of time, my humble recommendation to capable folks like yourself is not to dump too much on Unity and let's lighten their load.

    Please do not read these words as suggestions or opinions forced at you, I have had read many of your posts in different forums and we share many similary attitudes and Unity issues :)

    In summary, all `we` ask of Unity is to maintain the integrity of each single newly released bucket per published specifications. Any other functionality's burden in upon us.

    Dara
     
  3. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,650
    Any thoughts from the CCD team on the suggestion?
     
  4. llunity3d

    llunity3d

    Unity Technologies

    Joined:
    Aug 23, 2021
    Posts:
    24
    Hi @Peter77 ,
    Thank you again for your valuable feedback, we are currently evaluating options!
     
    Peter77 likes this.