Configure and manage Plastic SCM


关于如何在 Plastic SCM 中执行所有类型的任务的说明。

Administrator’s guide
Covers everything about configuring the server, installing, setup locks if needed, doing backups, archiving revisions, config files, and licenses.
Security guide
Learn how to perform basic security actions. This guide is full of examples that you can use to solve specific cases.
Version control for non-developers. If you need to work on a single branch with locks, use this guide.
This guide explains how you can customize Plastic's behavior. For example, learn how to enforce policies like ensuring branches follow a given naming convention.
Cloud extension
了解如何向 Enterprise Edition 添加 Cloud extension。了解我们的 Cloud 服务的工作方式。
Cloud Edition
了解如何使用 Plastic Cloud Edition — 托管式版本控制解决方案。
cm find
了解 Plastic 如何使用“cm find”查询分支、变更集和其他类型的对象。
Learn how to do component-oriented development with Xlinks.

Git interop

了解 Plastic 如何充当 Git 服务器和 Git 客户端。

说明如何设置 Plastic SCM 服务器,以便 Git 客户端将其识别为 Git 服务器。
说明如何将 Plastic 用作 Git 客户端并推送/拉取到 GitHub 或任何其他 Git 服务。
Plastic for Git users
If you're a Git user, find out what stays and what changes if you move from Git to Plastic.



Graphical user interface
A reference of the features in the GUIs.​
了解如何配置 Plastic 以便与 Jira 和 Polarion 等问题跟踪程序进行交互。此外,本指南还介绍如何自行创建与问题跟踪系统的集成。
External parsers
How to develop support for new languages for the Plastic semantic features.​​

DevOps with Plastic SCM

There are two main ways to implement DevOps in Plastic SCM: using mergebots or delegating the leadership to a Continuous Integration system.

DevOps driven by mergebots:
mergebot: the story of our DevOps initiative
Explains what mergebots are and how they can help you implement DevOps.
Add a mergebot to your repo
A practical example and tour through a working DevOps implementation driven by a mergebot.
Configure mergebots using config files
Explains how to manually configure mergebots without WebAdmin assistance.
Plastic SCM DevOps: Custom plugs
Explains how to develop plugs: the connectors between mergebots and systems such as Slack, email, etc.
Plastic SCM DevOps: Custom mergebots
Explains how to develop your own bots.
DevOps driven by the CI system:
A DevOps Primer
An explanation of DevOps and how it is implemented with Plastic.​
DevOps with Bamboo and Plastic
This guide contains a practical example explaining how to implement a DevOps cycle with Plastic and Bamboo.
DevOps with Bamboo: connecting to Jira
This guide expands on the previous example and explains how to take advantage of the extra info provided by the issue tracker.
DevOps with TeamCity
An alternative implementation of DevOps, this time using JetBrains' TeamCity CI system.

Blog highlights​

We regularly publish content on our blog. Here a few highlighted posts.

Plastic SCM vs. Git
How Plastic compares to Git.
All the software we write
If you want to learn more about the work we do and the software we develop.​
The story of Jet
Plastic’s super-fast repo storage. Find out why we use Jet as the default storage and why it is faster than the other alternatives.
CyberFlex - Jira, TeamCity, and Plastic integration
CyberFlex, one of our customers, share their CI implementation.
Track refactored code across files with Plastic SCM
It explains some of the semantic features in Plastic SCM.​
Using history to better explain branch differences
Delves into how Plastic enriches diffs with info from the file history.​
The history of version control
How version controls have evolved through the years.
Diff math
This blog explains some uncommon facts of very common diffs.​

The Plastic SCM API

查找用于在 Plastic 之上构建工具的选项。

Client-side REST API reference guide.
Server-side REST API reference guide. An easy way to automate Plastic.
一个可自动执行 Plastic 命令行的 C# 库。


If you are a Git user, check out this guide

Compare Plastic SCM with other version control systems in the Comparison matrix.


Commercial support is available through email. Check our pricing page for the option that best suits your team.

Community Edition users can find lots of useful information on our public forum. The forum is often monitored by the Codice staff as well as members of the Community.