Release BL647 introduced a great step ahead in the way in which branch (and cset) differences are displayed and explained. Now it is possible to understandwhere each difference comes from:

We are happy to announce a new Plastic SCM feature that allows configuring a server with encrypted data.

It means that, in your organization, you can configure a central server where all the data is encrypted. This way, the users who have a specific key, will be able to push/pull data to this server.

It is important to remark that this server is created for replication purposes only. Repositories have all data encrypted. If we directly download the file content to a workspace, we will only see empty files (the data is encrypted).

This configuration could be very useful when your server is accessible from a public network or you just need to be sure that even if a not authorized person access to your server, he will not be able get any information.

Microsoft defines Azure Websites as a fully managed Platform-as-a-Service (PaaS) that enables you to build, deploy and scale enterprise-grade web Apps in seconds. Since most modern web development teams promote new code from staging to production environments, it is important to consider various techniques to automatically deploy your code as part of your ALM (Application Lifecycle Management) process. The technique that we will focus on in this article is Plastic SCM with GitSync. With this technique, your team can quickly and easily publish changes automatically to Azure Websites from GitHub.

PlasticDrive is a tool to mount a changeset as a Windows drive and let you quickly browse the code using your favorite tools (Visual Studio, Eclipse, IntelliJ…). Files are downloaded from the server on demand (then cached) so the mount happens immediately, no need to wait for a big update to finish.

As you know Plastic SCM has awesome features built in but it is challenging to address users every need in a product of this type. So with that in mind, Codice Software created an automation layer called CmdRunner that allows you to easily and quickly query large amounts of information. The best way to show you how this works will be by example so we have chosen to integrate Plastic SCM with the Slack Bot API. We will use this example throughout this document to demonstrate all of the steps necessary to perform this integration.

Installing a Plastic SCM server on a small Raspberry box is a straightforward process. Once you get Mono setup, you can download our “zip server distro” and get it up and running in seconds.

This blogpost explains the process step by step.

Docker seems to be the new trend in application virtualization, and it is growing so fast that even Microsoft is getting ready to run Docker containers on Azure. They are also getting Windows ready to be dockerized.

This blogpost explains how to run a pre-built Plastic server Docker image that we have published at It explains the container structure we’ve prepared and how to isolate the server container from the data container to ease upgrades.