Plastic SCM

Unity Version Control (previously known as Plastic SCM) is a cross-platform commercial distributed version control tool developed by Códice Software for Microsoft Windows, Mac OS X, Linux, and other operating systems. It includes a command-line tool, native GUIs, diff and merge tool and integration with a number of IDEs. It is a full version control stack not based on Git (although it can communicate with it).

Features

Unity Version Control is a full version control stack platform. It includes these components:
* Server
* Command line client
* GUIs
* Diff and merge tools
* Web GUI
* Web-based admin interface

Some of its features include:
* Support for heavy branching and merging: According to its creators, Unity Version Control can handle unlimited branching and complex merge scenarios
* Visual Branch Explorer: A timeline to represent branches, merges and changes in repositories, implemented in all of its GUIs
* ACL-based security: Every object in the system can be secured with access control lists
* Built-in three-way merge and side-by-side diff including language-aware support and history of a specific method or function
* Directory versioning and support for versioning renames
* Revision history for branched, renamed, moved, copied and deleted files
* Blame/Annotate
* Centralized operation (SVN/Perforce style)
* Distributed operation (Git/Mercurial style)
* Atomic commits—the server assures that changesets are committed in the repository entirely
* ''Shelving''—users can save and restore work in progress for task switching
* Support for ASCII, Unicode, binary, symbolic link (on Unix), Mac-specific, and UTF-16 files
* Support for Mac OS X, Windows and Linux platforms
* Server-side and client-side event triggers
* High-latency network support: The network protocol used by Unity Version Control is optimized for high-speed/high-latency networks
* Gluon: GUI and workflow for non-developers (specially focused on game development)
* Locking: Binary files and assets that can't be merged can use locking instead of branching/merging

Design

Unity Version Control is a client/server system although in current terms of version control it can also be defined as a distributed revision control system, due to its ability to have very lightweight servers on the developer computer and push and pull branches between servers (similar to what Git and Mercurial do). Developers work on files in their client workspaces, and check in changed files together in changesets.

Storage

Unity Version Control has 2 different families of storage for all its data and metadata:
* Jet: An ad-hoc storage designed for high-performance, released with version 6.0. It is now the default storage.
* Relational databases: Traditionally Unity Version Control supported storing all data and metadata in relational databases: MySQL, SQL Server, SQLite, SQL Server Compact Edition, Firebird, Firebird Embedded, Postgresql and Oracle. Relational databases are still supported although Jet is now the default option.

Modes of operation

Unity Version Control can work in 2 modes:
* Centralized: With workspaces (working copies) connected directly to a server. Users perform checkin operations without the need for an additional push step.
* Distributed: Users host their own repositories on their computers and push/pull to a central server.

Differences from Git

Unity Version Control SCM is not based on Git although it can act as a Git server and a Git client. Differences can be summarized as: improvements in merge, native support for large files and projects, optional file-locking, can work distributed and centralized. There are differences in the branching structure too: while in Git branches are just pointers, in Unity Version Control branches are containers. Unity Version Control versions directories and files identifying them with "item ids" which is good for move/rename tracking, while Git relies on diffs to rebuild the renames/moves and doesn't version directories.

Interoperability with other version control systems

Git

Unity Version Control can interoperate with Git in the following ways:
* GitSync: Every Unity Version Control client can push and pull from a Git repository.
* GitServer: A Unity Version Control server can act as a Git server, so any git client can push/pull to a Unity Version Control server.
* Fast-import/export support: Fast-export and fast-import commands are available to export Unity Version Control repositories to Git intermediate format and import from Git intermediate format.

Perforce

Unity Version Control can do bi-directional sync with Perforce depots to ease migration

Other version controls

Import/export from other systems is achieved through Git's fast-import/export format.

Availability, release cycle and supported platforms

Unity Version Control is available to download from the Unity Cloud Dashboard or plasticscm.com. Major releases are published yearly as pre-built executables for Microsoft Windows, Mac OS X, and Linux.

Minor releases are available on a weekly basis.

Licensing and terms of use

Unity Version Control is free for individuals (Personal Edition), non-profit organizations and open-source projects (Community Edition).

Cloud Edition is a commercial version for teams that do not need an on-premise server. Customers pay per active monthly user and cloud storage. The subscription includes all the Unity Version Control software.

Enterprise Edition is a commercial version for teams over 15 users, typically used by corporations. It can be purchased in perpetual edition mode or with a monthly or annual subscription.

History

Codice Software started in August 2005 backed by an angel investor and the founders. The goal was to create a version control stronger than SVN in branching and merging and more affordable for SME than the commercial alternatives available at the time. In October 2006, they released the first version of Plastic SCM and was officially presented in Tech Ed 2006 in Barcelona.

In 2007, Codice was the first Spanish SME to achieve CMMI L2 using SCRUM.

Plastic SCM was featured by Novell as one of the companies using Mono commercially.

Plastic SCM 2.0 was launched in March 2008.

In 2009, Codice secures its first round of VC backed by Bullnet Capital, a Spanish firm specializing in tech companies.

Plastic SCM was a Jolt Award finalist in the Change and Configuration Management category, announced in December 2008.

Plastic SCM 3.0 was launched in July 2010 and it featured Xdiff/Xmerge: their first approach to track moved code in diffs and merges.

In December 2010, Plastic SCM announces "method history", a feature that allows the user to calculate the history of a given method/function instead of the history of a full file.

In 2011, Francisco Monteverde joined the company as CEO while Pablo Santos, founder, was appointed as CTO and President of the board.

Plastic SCM 4.0 was launched on November 23, 2011 and introduced a major change in the internal design: versioning and merge tracked was moved from a per-file approach to a per-changeset approach, which helped improving later Git-interop.

Since 4.0, Plastic started to be more oriented toward game development, specially considering the weaknesses of Git in terms of big repositories and files.

Version 4.1 was launched in April 2012.

In 2013, Codice launches SemanticMerge, a tool that diffs and merges based on code structure and not text. The technology was later integrated inside Plastic. Semantic builds on top of the previous work done on the Xdiff/Xmerge tool. Later that year Semantic added Java support to complement the initial .NET offering. Pablo Santos introduced cross-file diff and merge detection in QCon 2013 in San Francisco.

In 2013, Plastic SCM started natively supporting the Git network protocol, which virtually converts any Plastic installation into a Git client.

Plastic SCM 5.0 is launched in September 2013. It features built-in semantic diff, refactor detection and method history. Other features are path based security, client changelists and improved cloaked rules.

Version 5.4 later expands some of these features and add a few more: encrypted servers, JavaCLI (a Java client to support HP-UX and Solaris scripting), multi-core file upload and download, Plastic Gluon (developed in collaboration with Telltale ), a GUI for artists in game development, WAN optimized data transfer, submodules, transformable workspaces.
Plastic 5.4 evolves as Plastic's primary version and in December 2014 a new native GUI for Linux is launched replacing the previous cross-platform one. 5.4 includes a new native MacOS GUI too.

In January 2016, Plastic Cloud was launched as a cloud repo hosting system.

In March 2016, Plastic Cloud Edition was launched, a new version designed for teams who do not need an on-premise server.

Version 6.0 was finally released in January 2017. It features a new data storage system called Jet, full backward compatibility up to 5.0 and floating licenses support. 6.0 continues evolving during 2017.

Plastic SCM 7.0 was launched in March 2018 including a new Branch Explorer design, new web-based administration interface, and improvements in MacOS and Linux GUIs.

The mergebots feature was launched in September 2018. Mergebots are a way to implement DevOps with server-side agents that detect when branches have to be merged after testing them on a CI system.
Plastic SCM 8.0 was released in January 2019.

On August 17 2020, it was revealed that Unity Technologies, the creators of the game engine Unity, had acquired Codice Software.

See also

* List of revision control software
* Comparison of revision control software

Notes

References

*
*
*
*
*
*

{{Revision control software

2006 software
Proprietary version control systems
File comparison tools