Distributed Version Control for Big* Software

Distributed Version Control for Big* Software

*Big - if you’re building large scale software, involved on a project that is critical to your company, you’ve to handle huge files or need to run complex merges, then Plastic SCM can help you keeping things under control.

What you can do with Plastic SCM

A version control system that will help you develop new features in parallel,
go distributed, merge in time, and never break a build again

Develop huge projects & binaries

Develop with Task Branches

Distributed and multi-site

Develop video games

Develop video games with artists and developers using the same version control for large binaries and code

Do continuous delivery

Do continuous delivery

  • Work in branches, test and peer-review every branch before merging.
  • Use release branches or ‘main’ to deliver.
  • Plug any CI system you want.

Why Plastic SCM?

1 Real DVCS without the shortcomings

1 Because you get a real DVCS without the shortcomings.

Teams worldwide are moving to distributed version control and then they find:

  • Plastic is the only DVCS designed from the ground up for companies, while all the others come from an open source background.
  • None of the other enterprise oriented products can’t do real distributed version control and many are weak with branching and merging or perform poorly under heavy load.

And Plastic can handle what the open source DVCS can’t:

  • Teams that need to handle huge binaries (like happens with game developers.
  • Teams working on large projects (>300k files) and unmergeable content.
  • Developers that need a good GUI and visualizations.
  • Teams that need the ability to work centralized or even have entire groups at different multi-site locations, and they need a system that scales.
  • Companies that require extended security.
  • While they can still sync with Git.
  • You can think of Plastic as a superset of the open source DVCS that adds extra features (although it is not based on them).
Real DVCS without the shortcomings

2 Better branching and merging

2 Because you need much better branching and merging.

  • Many teams are moving to “task based development”. Having good branching and merging is a core requirement in order to implement it.
  • Teams need to create branches in milliseconds even with huge codebases, and merge them back easily.
  • “Branching and merging” is not new, it has been around for decades, but really few version controls can do it well.
  • The Plastic core is all about branching and merging. Is what we call the “merge machine” and it clearly beats other products.
  • And we also develop all the other tools around: from the GUI to handle the merges to Xmerge and SemanticMerge the only one that understands the code.
Real DVCS without the shortcomings

Some of our customers

Some of our customers

Plastic SCM compared

Find out how Plastic compares to some of the most widely used version control systems and choose your way to Plastic

What is new in Plastic SCM 5.0

Every new release of Plastic SCM comes with a long list of improvements. Here are some of the most relevant new features:
  • GitSync

    Plastic SCM now speaks the Git network protocol so it is possible to directly push and pull from a remote Git server, including GitHub.

    plastic scm, screenshot of GitSync
  • Item merge tracking

    Diff a branch or a changeset, show the 2D-file history or annotate a file and find how merges are better explained.

    plastic scm, screenshot of Item merge tracking
  • Semantic History

    90% of the time when you check a file’s history, you are only looking for a specific method. Semantic History parses the code and tracks the element you’re looking for

    plastic scm, screenshot of Semantic History
  • Client changelists

    A way to organize in groups the checkouts on the ‘pending changes view’.

    plastic scm, screenshot of Client changelists
  • Visual Studio 2013

    Tightly integrated with the newest release of Visual Studio, including the new color schemes.

    plastic scm, screenshot of Visual Studio 2013
  • Improved Eclipse support

    New built-in Branch Explorer, performance improvements, new queries on views and lots of small tweaks.

    plastic scm, screenshot of Improved Eclipse support
  • New path based security

    Now you can assign ACLs to paths so you can easily enforce policies on certain areas of your project source code tree.

    plastic scm, screenshot of New path based security
  • Improved annotate / blame

    Blame is now more precise than ever and it shows more information like the major contributors to the file and the average line age.

    plastic scm, screenshot of Improved annotate / blame
  • Java command line client

    A Java-based, fully featured, command-line client has been added to support platforms like HP-UX and AIX.

  • Improved cloaked / ignore rules

    The rules to define cloaked.conf, ignored.conf and hidden.conf files are now more flexible and simpler to define.

If you’re a smaller team, get started today, and be ready for when your project grows!