Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Bug Plastic SCM Login Expiration Times Are Ridiculous

Discussion in 'Unity Build Automation' started by ZO5KmUG6R, Apr 5, 2022.

  1. ZO5KmUG6R

    ZO5KmUG6R

    Joined:
    Jul 15, 2010
    Posts:
    490
    Every 2-5 days cloud builds are failing, and then our auto builds are getting auto turned off by Unity because "lost access to Plastic, please re-authorize"

    This is beyond frustrating, especially because it takes 30-45 seconds to edit builds with Plastic SCM because it takes that long to load your branches.
     
    Brogan89 and IOU_RAY like this.
  2. Brogan89

    Brogan89

    Joined:
    Jul 10, 2014
    Posts:
    244
    Yes, agreed, why does this even need to happen? Just set it up once and forget about it.
    Please change this UCB team :)
     
    LilGames likes this.
  3. ollieblanks

    ollieblanks

    Unity Technologies

    Joined:
    Aug 21, 2017
    Posts:
    459
    Hi both,

    I agree this is very frustrating. I suspect this is a bug with Plastic SCM that is catalysed by Cloud Build when it invalidates its own cache.

    Thankfully, there is a pretty easy workaround to this. Next time you are forced to update your Source Control configuration use a Plastic SCM password instead of your Unity ID for authentication (If you don't have a Plastic SCM password, create one with the Forgot Your Password function at plasticscm.com).

    With the standard Plastic SCM authentication there is no need for auth tokens and therefore no more token expiry.

    Hope this helps!
     
    Brogan89 likes this.
  4. ZO5KmUG6R

    ZO5KmUG6R

    Joined:
    Jul 15, 2010
    Posts:
    490
    Not really. That will be yet another nonsensical thing in the Unity ecosystem. You force us onto new source control THEN force us to make plastic accounts as well.

    This was not an issue since the launch of Plastic, and only started a week or two ago.

    Basically the current Cloud Build instructions for Plastic, which as Unity said should be "hassle free" are
    - Make a plastic account, despite having the option to login with a Unity ID
    - Enter your repository source, which I couldn't find any clear documentation for except a 5 year old plastic forum post saying to use "cloud@whatever"
    - Disable auto version detection on build targets, as this just does not work with Cloud Build and causes a build failure due to "Unknown error"
    - Repeat the above step at 30-45 seconds per build target because the 'branches' take forever to load and if you don't let them load the website softlocks. This step totals several minutes if you use Unity anywhere above a personal capacity.
    - Finally your "hassle free" setup is done

    For being the new technology Unity has deemed release ready and moved us onto, this is absolutely bizarre.
     
    Last edited: Apr 7, 2022
    LilGames and IOU_RAY like this.