Step 3: Migration completes and the button is replaced with a button to open Plastic SCM window Step 2: Unity editor pops up a Plastic SCM migration wizard. Step 1: Unity converted our projects to Plastic SCM I think this is the very first thing newcomers to Plastic SCM will face after this migration, yet it doesn't seem to be addressed in any of the guides. Watch this short video tutorial to learn how to work in the Unity Editor and replicate some of your previous tasks from Collaborate in Unity Plastic SCM.Īnd what does 'added and private' mean and what should I do about those files? Collaborate User's Guide to Unity for Plastic SCM After the upgrade, Cloud Build will need to still be configured to use your Plastic repository. If you are not using one of the supported Editor versions above, you can still use Plastic SCM’s full functionality by downloading the full Plastic SCM client.Ĭonnecting your projects to Cloud Build after the upgradeĬloud Build doesn’t change its linked repository from Collaborate to Plastic SCM automatically. Work using the Plastic SCM client for unsupported Unity versions Supported Editor versions are the following: If you are using one of the supported Unity versions below, you will be able to resume working using Plastic SCM for Unity. Work in-editor with supported Unity versions Here are links to resources to help you get started with Plastic SCM after the Collaborate upgrade.

Unity cloud build with plastic scm