Official Announcement: Unity Teams and DevOps vision

The goal of the Unity DevOps team is to provide our users with cloud-based DevOps tools to help them release more often and catch issues faster. That’s why today, May 5th, there are important changes coming to how all new users will interact with Unity DevOps tools.

Today, we’re releasing a new metered version of Cloud Build. It includes expanded storage and concurrency limits plus a host of UI improvements so you can efficiently automate multi-platform builds in the cloud.

We’re also retiring the ability to purchase new Unity Teams bundles, and, as a result, Teams Advanced will not be tied with brand new Unity Pro, Unity Enterprise, and Unity Education subscriptions starting today. This move will not touch current subscribers to Teams or Teams Advanced. We’re doing so to enable more freedom of choice to our users, who can choose to enroll in Plastic SCM and metered Cloud Build at any time.

You can read more in today's blog post about our DevOps vision.

Roadmap and Customer Advisory Board
If you'd like to get involved, we invite you to sign up here for a chance to work closely with us to guide the future of DevOps for real-time 3D. Or view and give feedback on our DevOps roadmap and multi-year plans here.

Frequently Asked Questions:

Q: Why is Plastic SCM being prioritized over Collaborate going forward?

A: Collaborate was never designed to be a fully-featured VCS solution, which Plastic SCM is. The Plastic SCM technology is also a better fit for Unity creators’ needs, since it was designed specifically for real-time 3D, with separate workflows for artists and programmers, and support for handling large files and binaries common to RT3D development.

Q: What’s happening to the versions of Unity Teams bundled into Unity Editor subscription plans?
A: Starting May 5, 2022, new subscribers to Unity Pro and Enterprise will no longer receive any allocation of Unity Teams. You can take advantage of Plastic SCM’s cloud edition for version control, which is free for up to three users and 5 GB per month, and then pay as you go pricing. Cloud Build has pay-as-you-go pricing.

Q: What are Unity’s current DevOps offerings?
A: Currently, there are two separate components, each available for purchase separately – Plastic SCM for version control and Cloud Build for CI/CD.

Q: As an existing Cloud Build customer, will my pricing change?
A: No, it won’t change. As an existing Cloud Build user, you will continue to have access to your current pricing and capabilities for the foreseeable future and until we move all Unity products to Cloud Build 2.0. You will receive notice 60 days in advance of changes to your account prior to conversion to Cloud Build 2.0. Note that access to larger repositories and increased concurrency limits will be unavailable if you choose to keep the old Cloud Build pricing, along with many of our planned innovations.

Q: How does the new Cloud Build pricing work?
A: Cloud Build 2.0 pricing is completely metered. You will only pay for what you use. Users are charged for build minutes, based on the platform they are building for. For Windows the price is $0.02/min; for Mac the price is $0.07/min; and it’s $10 per build machine concurrency.

Q: Can I use version control in Unity, or do I need a separate client?
A: Unity Plastic SCM works in the Unity Editor, and it can also be accessed via a separate desktop client. In supported versions of the Editor, Plastic SCM users can check-in, check out, lock files, view file history, and even create and switch branches as well as choose to install a separate desktop client. For former Collaborate users, see this user’s guide to switching to Plastic in Unity. A list of supported versions for the in-Editor experience is available here.

Q: Can you use Cloud Build with Plastic SCM?
A: When setting up Cloud Build, you can choose to connect to Unity Plastic SCM as your source control. If you previously used Collaborate for this workflow, you will need to take action to connect Cloud Build to Plastic SCM. Follow this guide here.

Thanks!

The Unity DevOps Team