Plastic SCM

Plastic SCM
Name	Plastic SCM
Developer	Codice Software / Unity Technologies
Released	2005
Latest release	2024
Programming language	C++
Operating system	Windows, macOS, Linux
License	Proprietary, Commercial

Plastic SCM is a distributed version control and source code management system designed to handle large binary assets, branching workflows, and team collaboration for software and game development. It emphasizes graph-based branching, visual tools, and scalability for repositories with large file counts and big files, positioning itself for studios and enterprises requiring concurrent asset management and continuous delivery. Plastic SCM combines elements of distributed and centralized version control paradigms to support both local workflows and server-based collaboration.

Overview

Plastic SCM provides a version control platform that supports branching, merging, and artifact storage for teams across software, Unity, Epic Games-powered projects, and multimedia studios. It competes with systems such as Git, Perforce, Subversion, Mercurial, and Bazaar by targeting scenarios where large binary files, complex merge histories, and visual history inspection are critical. The system exposes both command-line and graphical clients and integrates with continuous integration tools like Jenkins, GitLab CI, and TeamCity. Plastic SCM emphasizes visual branch topology akin to representations used by Graphviz-style visualizers and supports server setups that mirror designs seen in AWS deployments and Microsoft Azure infrastructures.

History

Plastic SCM originated in 2005 at Codice Software, founded by engineers with experience in enterprise projects and game development workflows. The project evolved through adoption by independent studios and enterprises, gaining traction alongside engines such as Unity and toolchains from Autodesk, especially in industries where digital asset management intersects with source control. Over time Plastic SCM developed features to address limitations observed in centralized systems like Perforce Helix Core and distributed systems such as Git. In 2020-2021 Plastic SCM attracted attention from larger corporations and development communities, culminating in closer collaboration with firms such as Unity and expanded cloud service integrations. Its evolution reflects trends observed after influential events like the rise of distributed workflows popularized by Linus Torvalds and the adoption patterns of projects like Linux kernel and large game productions.

Architecture and Features

Plastic SCM uses a DAG (directed acyclic graph) model for commits and branches, enabling explicit branch lineage and merge tracking similar to models used in systems influenced by DAG-based version control research and applied in projects such as Bazaar derivatives. Its architecture supports distributed clones, central servers, and hybrid topologies deployed on platforms like AWS, Azure, and on-premises clusters. Key features include Large File Support (LFS-like capabilities), lightweight branches, semantic merge tools, 3-way and 2-way merges, and a commit graph visualizer inspired by enterprise visualization tools used at Google and Facebook. Plastic SCM provides per-branch locking mechanisms familiar to studios using Perforce for binary asset protection, plus shelving, cherry-picking, and replication. It implements transport layers compatible with protocols used by SSH and HTTPS, and offers metadata handling suited to digital asset pipelines employed by Pixar and major VFX houses.

Usage and Workflow

Teams adopt Plastic SCM for workflows centered on branching strategies—feature branching, task branches, and long-lived release branches—comparable to practices promoted by Git Flow and trunk-based models advocated in CI literature. Developers use the GUI client to visualize branch topology and perform merges, while DevOps engineers script operations through the CLI and RESTful APIs to integrate with Jenkins, GitLab, and orchestration platforms such as Kubernetes. Game studios combine Plastic SCM with asset pipelines from Autodesk and content creation suites by Adobe for large binary handling. The system supports code review patterns paralleling those found in Gerrit and Phabricator-based workflows and can coordinate releases alongside project management tools like Jira.

Integrations and Platforms

Plastic SCM offers integrations with IDEs and engines including Unity, Unreal Engine, and development environments such as Visual Studio, JetBrains Rider, and Eclipse. It connects with CI/CD tools like Jenkins, GitLab CI, and TeamCity, and works with artifact and package registries similar to Artifactory and Nexus Repository. Cloud hosting options leverage services from AWS, Microsoft Azure, and GCP. Platform clients support Windows, macOS, and Linux distributions and integrate with authentication providers and directory services such as Active Directory and OAuth providers used in enterprise environments.

Licensing and Editions

Plastic SCM is distributed under commercial licensing models with editions tailored for small teams, studios, and enterprise deployments; offerings include cloud-hosted services and on-premises servers. Editions provide varying features such as repository size limits, user counts, and advanced functions (replication, high-availability, and enterprise authentication). Licensing options and pricing models follow structures comparable to commercial products from Perforce and Atlassian vendors, with enterprise agreements facilitating integrations into compliance regimes used by organizations like ISO-certified firms and regulated industries.

Reception and Industry Adoption

Plastic SCM has been adopted by game developers, VFX studios, and enterprise engineering teams that require robust handling of large binary assets and branching visualizations. Industry commentary often contrasts its strengths with those of Git for code-centric projects and Perforce for traditional game asset management, noting Plastic SCM's niche in combining distributed workflows with centralized control features. Adoption case studies reference studios and companies that have transitioned from legacy systems to Plastic SCM to streamline collaboration across geographically distributed teams, reflecting similar migration narratives seen in moves from Subversion to modern version control systems. Critical reception highlights the product's visualization tools, large-file performance, and workflow flexibility while noting considerations around licensing and integration overhead in complex enterprise environments.

Category:Version control systems