Choose your way

All software teams use a version control, so if you’re looking at Plastic SCM chances are you’re considering to move away from yours. Find out what you should consider depending on your current version control.

From ClearCase

ClearCase is still one of the most widely used SCMs. It is very strong (especially base ClearCase) but it is also expensive and cumbersome to use. Plastic SCM will make “base CC” users feel at home while removing all their daily issues. You will only miss dynamic views.

Why would you migrate away from ClearCase?

If you’re considering to move away from CC chances are you are considering some of the points on the following list:

  • You need better network performance especially on networks with higher latency.
  • Operations don’t run fast enough and the entire team can’t stand the waiting times.
  • Price is a concern.
  • You need lighter and faster distributed support because multi-site is not enough anymore or not even an option.
  • Distributed – Plastic SCM is fully distributed, much better than CC MultiSite and with no added costs or administration overhead.
  • You need better and faster merging (some merge operations taking much longer than they should).

This is what Plastic SCM offers you:

  • Network performance – Plastic SCM operates on a single port and scales better - View more
  • Plastic SCM operations (checkin, checkout, workspace creation and update) run much faster than in CC.
  • Pricing is not a concern because Plastic SCM is much more affordable than CC.
  • Plastic SCM is fully distributed, much better than CC MultiSite and with no added costs or administration overhead.
  • Much better and faster branching and merging (including branch-per-task - View more ).
  • And the newest merge technology – Semantic Merge For a full list visit: Our blog

From Perforce

Perforce has been around since 1995 and is one of the strongest commercial version controls. It is the most widely used SCM in the gaming industry.

If you’re considering to move away from Perforce you probably have the following issues:

  • Need to do intensive branching and merging that P4 (even the newest version) can’t really handle.
  • Need to connect distant teams using true DVCS.
  • Need to increase scalability and avoid database locks and have everyone in the team working faster.

But you can’t go for a regular DVCS because:

  • You require “exclusive checkouts” / locking.
  • Your project has to deal with huge files.
  • Part of your team needs to work centralized.

What you get in Plastic SCM is:

  • The strongest branching and merging engine - View more
  • Full DVCS support
  • Scalability under heavy load - View more and a wide variety of standard database back-ends which you’ll prefer to P4 Berkeley DB - View more
  • Plus the ability to handle locks, huge files and work centralized.
  • And the newest merge technology –View more

From Visual Source Safe

If you’re using VSS then you don’t have many options: move! It doesn’t really matter which one you choose, any version control is better than good-ol SourceSafe. Moving away will be like evolving from the prehistory to modern days so maybe you can save middle-ages by directly jumping into a modern DVCS.

What you get (in almost any modern SCM, not only Plastic SCM):

  • Branching & reliable merging – it will be like stepping into a brand new world full of possibilities.
  • Speed – every operation will now be faster.
  • Reliability – your repository won’t break.

And, after that: distributed, better visualizations, branch-per-task and many more.

From Git

Git is the most widely adopted DVCS. It is strong with branching and merging, fully distributed and well documented.

Why would you migrate from Git to Plastic SCM?

If you’re using Git chances are your team adopted it in the last 2-3 years so it is probably too soon to move away (typically a version control, once adopted, is not replaced before 4-5 years).

If you’re considering to move away probably you’ve at least one of the following issues:

  • Your team needs to handle huge binaries, which is one of the well-known Git weaknesses.
  • You need locking (exclusive checkout) to manage non-mergeable files (like graphical assets on games).
  • Part (or all) of your team needs to work centralized.
  • You need even better merging – with precise move tracking.
  • Your team needs more intuitive tools (especially on Windows).
  • You need stronger security.

This is what Plastic SCM offers you:

  • Huge binary file support.
  • Support for locking (exclusive checkout) even on distributed scenarios - View more
  • Works centralized and also distributed.
  • The strongest merge engine - View more - able to deal with cases out of Git’s scope.
  • The best visual tools, including the branch explorer - View more
  • ACL based security - View more
  • GitSync – to coexist with Git repositories - View more
  • Support for fast-import & fast-export to ease migration. - View more
  • And the newest merge technologyView more

From TFS

TFS is much more than a version control. It is a full-featured ALM. But when it comes down to the version control part, TFS is not the strongest contender.

Why would you migrate from TFS to Plastic SCM?

If you’re evaluating Plastic SCM to move away from TFS most likely you have one or more of the following points in mind:

  • Your team needs multi-platform support – you can’t just restrict yourself to Windows anymore.
  • You need stronger and faster branching and merging.
  • You need distributed development with good Windows GUI tools and Visual Studio integration.

This is what you will find in Plastic SCM:

  • Support to run client and servers on Windows, Linux and Mac OS X.
  • The strongest merge engine - View more
  • The best visual tools, including the branch explorer - View more and strong Visual Studio integration - View more
  • And the newest merge technologyView more

From Subversion

SVN was the Open Source version control with greatest adoption and peaked about 5 million users worldwide... and then the distributed version control revolution entered the scene and every major OSS project moved away from SVN. Now the industry is following.
Subversion is still widely adopted so chances are that if you are here, you’re looking for a SVN replacement...

Why would you migrate from Subversion to Plastic SCM?

If your team is considering to move away from Subversion then most likely you’ve one of the following issues:

  • You need stronger and faster branching and merging.
  • You need distributed development
  • You need better performance and scalability under heavy load

This is what you will find in Plastic SCM:

x

ClearCase

Why would you migrate away?

1
Network performance and overall speed.
2
Too expensive.
3
You need dvcs and better merging.

What Plastic SCM offers you

1
Network and overall performance.
2
Affordable.
3
Full DVCS plus centralized and the best merging engine.
x

Perforce

7
55

Why would you migrate away?

1
Need intensive branching and merging.
2
Effective distributed development.
3
Scalability.

What Plastic SCM offers you

1
The strongest branching and merging engine.
2
Full DVCS plus centralized if needed.
3
Skyrocket scalability.
x

Visual Source Safe

Why would you migrate away?

1
Old, slow, error prone.
2
No branching or merging.

What Plastic SCM offers you

1
Just move away from SourceSafe ! :-).
x

Git

5
60

Why would you migrate away?

1
Gaming features: big binaries (>500Mb), locking.
2
Even better merging.
3
Security.

What Plastic SCM offers you

1
Huge binary support.
2
The best merge engine.
3
ACL security + visual tools.
x

Team Foundation Server

6
40

Why would you migrate away?

1
Need multi-platform.
2
Need for stronger branching and merging.
3
Distributed development.

What Plastic SCM offers you

1
Windows, Linux and MacOS.
2
The strongest branching and merging engine.
3
Fully distributed and also centralized.
x

Hg

5
40

Why would you migrate away?

1
Gaming features: big binaries (>500Mb), locking.
2
Better merging (including recursive).
3
Better security.

What Plastic SCM offers you

1
Huge binary support.
2
The best merge engine.
3
ACL security, visual tools, exclusive locks.
x

Plastic SCM

11
85

Astonishing visualization

1
Industrial-strength branching and merging engine.
2
Fully distributed and also centralized.
3
Fine grained security.
4
High scalability.
5
Enterprise-ready database backends.
x

Subversion

5.5
0

Why would you migrate away?

1
Need stronger branching & merging
2
Need distributed development
3
Need speed and scalability

What Plastic SCM offers you

1
Industrial strength branching and merging
2
Full DVCS
3
A super fast and scalable solution

Get the latest news