What is Plastic SCM
Plastic SCM is the best Distributed Version Control supporting task-driven software development for teams of any size because it simplifies branching and merging.
It works the way you want!
- Fully Distributed or Centralized repos
- Branching and Merging made Simple
- Powerful GUI or straight command line
- Reliable & Scalable Repo Storage with the RDBMS of your choice
Who is it for
Plastic SCM is for developers who love the freedom of distributed and simple branching and merging. It is for managers who need to lead distributed teams and understand the status of the project. And it is for release builders who need to create stable releases.
Plastic SCM is the only version control system that can meet the demands of globally distributed development. It easily scales within any sophisticated development environment, without friction or complexity. It's SCM made simple.
What makes Plastic different
Three key aspects of Plastic SCM's architecture make it superior to other systems:
- It has excellent support for task-driven parallel development.
- It's a true distributed version control system (DVCS). Code branches can be replicated to multiple sites graphically with a single click.
- Awesome graphics, providing visualization of data and procedures that greatly simplifies even the most sophisticated version control operations.
Some of our customers
Benefits of using Plastic SCM
Graphical tools
The graphical tools greatly help visualizing change. And because your code is constantly evolving, it's very important to see where changes happen, where do they come from (even exploring remote locations!) and what code got into a given release.
The distributed branch explorer is a complete and interactive representation of the evolution of your project, able to display the changes happening in remote servers together with the local ones. Get the remote changes from your colleagues and merge them with yours just by right clicking. All in a single diagram offering a global view of the fully distributed environment.
Graphical Diff of changesets, branches or labels
The graphical 3-way merge tool, with moved code detection and Xmerge to ease conflict resolution after refactors.
No more broken builds
Enforce the release-early/release-often agile best practices and avoid broken builds forever:
Using task driven development you get Continuous Integration on Steroids: validate changes before breaking the build instead of reacting once it is broken. Avoid bug propagation!
Thanks to our awesome branching and merging, you can isolate tasks in their own branches and avoid developers getting impacted by their colleagues' mistakes. Since tasks are short-lived, you merge them together to form releases often, following the agile recommendations.
Plastic SCM is designed to support thousands of branches through its DAG-based architecture.
Fearless refactor
Plastic SCM tracks and merges moved and renamed files or folders perfectly. No more problems to use branches and refactor together.
Our awesome branching and merging support ensures that everything is in the repository and that files added, removed, renamed or moved are correctly merged between branches.
Support distributed teams
From remote offices to single developers working at home, Plastic SCM is a fully distributed system that lets you replicate your code semalessly between repositories.
Plastic SCM servers can replicate complete or partial repositories and, since the servers are very lightweight and installed in less than a minute, you can have your own partial or full copy of the code you need right in your laptop.
Reuse components
Thanks to the new Xlinks technology, you can now easily reuse libraries and other shared components between projects just by splitting them into repositories and mounting them on the needed folders.
When you have to modify the mounted component, we provide automatic branch expansion, so you keep working transparently and your changes are safely recorded in a separate branch that doesn't affect other users of the component. Of course, the new branch can be seamlessly merged.
Don't let the version control tool get in the way
With Plastic SCM 4.0 we introduce transparent SCM so you don't have to tell the SCM what you are doing: you can move files around, rename, change, add or delete them. When you are ready to commit your changes (or check-in, as we say), Plastic SCM will detect all the operations you did and display them, so you can check them in with one click.
Interoperability with other systems
Plastic SCM 4 supports the fast-import / fast-export interchange format to communicate with your existing version control system, making migration or even co-existence a smooth and pleasant walk.
Furthermore, Plastic SCM integrates with IDEs, editors, issue trackers and many third party tools.
