We take pride in many things: delivering an innovative product and changing the version control landscape one task at a time is one of them, for example; keeping together the same team since day one; growing year by year our client and user base...

If there is, though, one common trend to all those things it's that everything we do, we do with passion. We put our hearts and souls on what we do. Plastic SCM is thought and designed to enable its users to take their skills to another level. It is architectured to seamlessly integrate in your toolset and help you craft code. Be it because our users start using task branches, or because they are able to coordinate distributed teams without friction or, finally, because they implemented some automation in their DevOps pipelines.

Whatever it may be, they will eventually require help. Because version control is not easy.

Psst Gluon (picture from Commit Strip, September 12th 2017)

Wait... What? Is that Octocat?

Is Plastic SCM version 8 a new GitHub product? No!! This is our small homage to our dear colleagues at GitHub.

Plastic SCM version 8 is out and we wanted to play around with Octocat and our own Owl mascot. We have named it circumstantially and just for today, Octowl.

We've been busy lately and despite the holidays season taking away half of our team during the first week of January, we have been able to release some goodies and fix some buggies ;-) You can always refer to our publicly available Release Notes section in our site.

In this post, you find a briefly narrated, clear explanation of what has been released during this month.

We are happy to announce the release of GuiTestSharp, an open source GUI-test framework used to automate the testing of desktop apps written in C# on Windows, Linux and macOS.

As far as we know, it might be the first cross-platform GUI testing framework for .NET/Mono/Xamarin.

You can see it in action here:

And grab the source code now from its GitHub repository

We've been using this framework internally for years with success to test our Windows Forms, GtkSharp, Xamarin.Mac and WPF applications.

The framework itself is quite thin, and you simply have to fill a number of "test interfaces" to actually make your app testable.

This blogpost and the GitHub repository are the starting points to show you how to best use it and start GUI testing your C# applications.

We'd really like to find other teams who find it as useful as we do!

Today, I bring to you a blogpost that is long overdue. If you are a DIY enthusiast like me, you probably have a bunch of Raspberry Pi's lying around. Who knows, maybe Santa (or the Three Wise Men, or your local traditional gifter) brought you one these past holidays. If you want to put one to good use, and you already have your very own CandyVault up and running, maybe this software-only project is a good one to take over the next weekend!

By the end of this post, we will have a Plastic SCM server and client installed on our Raspberry Pi, we will have automatic upgrades, cloud-based repository backups, and the cool thing is, we will get notified on our smartphone every time one of these events occur through IFTTT)!

CyberFlex Software is an Australian software company that has been developing software for the Heavy Glass, Automotive and Transport industries since 2001.

We've been using Plastic SCM for around 10 years now and have always been happy with the approach Plastic SCM takes to source control and customer service.

Right now, we use Plastic SCM in a fully distributed configuration leveraging the Plastic Cloud offering by using it as our central repository with each developer having their own local repository.

In this blogpost, I want to show you how this configuration works well for our team who work across multiple offices and allows for flexible working from home if required.

We are happy to announce we have a new mascot!

A clever owl that represents a wise librarian. As version control developers, we love the idea of Plastic being the librarian of your projects, and a wise one indeed :-)

Plastic SCM new mascot

Do you suffer from the occasional illness of "Ouch! The changes I did few days ago were rejected because of merge conflicts?" On a scale of 0 to 10, how annoyed are you when you have to go back to that code and fix these silly conflicts? If your answer is, let's say, 7 or greater, continue reading, and maybe you will discover an interesting proposal to take care of them at the early stages.

A DevOps medication

If you are a DevOps-aware team, you are probably familiar with concepts like Continuous Integration (CI) and Trunk-based-development, and the benefits they provide to your value stream.

You may also know how important it is to keep flow moving fast and to have instant feedback for your rejected code changes in the pipeline for any reason, so the cause of the problem is addressed sooner, before it becomes a tedious task.

But implementing processes to fit these needs could be a major step. I'd like to show you how Plastic SCM leverages its DevOps feature to easily create an actual ecosystem of automation bots to achieve all of these goals.