As a Plastic SCM administrator, you had probably spent some time struggling with your company users activation and finding a way to assign your licenses as effective as possible.

In this blog post, we will explain you all the manage users commands and how you can benefit from them.

The BL717 comes fully loaded with improvements. Together with the Mac mergetool we have included a bunch of improvements on Windows for the diff and merge tools.

Here goes a screenshot to see how it looks like now:

We launched BL717 a few days ago, including the new native mergetool for Mac (a.k.a. macmergetool).

It is the long awaited Coca-based 3-way merge tool, a different GUI implementation for the same merge core shared by the Windows and the recently launched Linux version.

You can see it in full glory in the following screenshot:

I’m going to explain how I take advantage of Plastic Drive to help during code refactors.

What is Plastic Drive

In case you don’t know, it is just a way to “mount” the contents of a changeset as a Windows Drive. It is a “readonly” mount, so it is not like a real workspace. But it is useful to browse code using your favorite tools (Visual Studio in my case).

We're launching BL707 today and it includes one highly awaited feature: the Linux GUI now includes its own native 3-way mergetool (a.k.a. gtkmergetool).

Hi there! My name is Göran Wallgren and I was invited to write this guest blog post to share how we switched our version control system from SVN into Plastic SCM. I work at Surgical Science (Sweden), where we have been developing products for medical simulation training for more than 15 years.


We started out using CVS for version control, and then migrated into SVN (Subversion) and TortoiseSVN almost 10 years ago. In summer 2015 we finally decided to migrate into Plastic SCM. Besides the advanced merging and handling of large binary files, one of our main reasons for choosing Plastic over Git or Mercurial was that it can work both centralized and distributed (DVCS), which made the switch from SVN easier. The changeset numbering scheme is also closely resembling the one in SVN.

At the point of migration, we had close to 28000 revisions from 14 years of code and data history in our main SVN repository (ca 20 GB). We wanted to keep all revisions from trunk but decided to leave out inactive branches in the import and also to split some parts into separate repositories in Plastic. In the end, this left us with a bit over 17000 imported changesets in the main Plastic repo.

Migration would have to go via Git, since Plastic won't import directly from SVN. Earlier, one had to use Git fast-export and Plastic fast-import which had some issues (mainly since Git does not log directory removals in the fast-export file). However, that has all changed with the Plastic GitSync feature that means Plastic SCM can now speak directly with Git over the HTTP/HTTPS and GIT protocols.

Besides the actual import of the data, we needed to find ways to replace some of the features we had been using in SVN, mainly svn:externals and the SubWCRev tool from TortoiseSVN. At the end of this post we'll give some useful tips regarding this.

You're coding on your laptop (anywhere but the office), you checkin to your local repo, and then you want to share it with your colleague bob for a quick review.

One option is to go and push to the central server, then ask bob to pull from there. Not bad, the usual cloud based server placed somewhere.

Another option is to find out bob's public IP address, ask him to tweak the router so his Plastic server becomes reachable and... well, we won't go that route…

Wouldn't it be just awesome if you could simply do something as follows?

Locate bob's repo just using his email, no matter where he is, as soon as he is connected to the internet.

This way it won't matter whether you both are behind firewalls, or if you switch locations, you'll be always reachable.

This way to reach Plastic SCM servers is what we called The Tube and we opened it up for beta testing back in May 2015.