- Home /
- Plastic SCM Enterprise Edition, per user, per year
Plastic SCM Enterprise Edition, per user, per year
Out of stock
| SKU | plasticscm-enterprise |
|---|---|
| Status | Enabled |
Less work in progress
More tasks delivered
Plastic SCM is a version control to help teams focus on delivering work, one task at a time.
A few things you can solve with Plastic SCM
Game development
Big files, huge projects, Unity and Unreal? Tired of Perforce and can’t go to Git? We got you covered – learn more.
Artists need a simpler tool, locking and hate branches? Check Plastic Gluon.
Host your projects in the Cloud
We host your repositories online so you can forget about server maintenance and upgrades. Even when your repos are in the hundreds of GB range.
Team infrastructure
Distributed team? Covered.
Need to work centralized? Solved too.
Need strong branching and merging? Checked.
Scale Git-like workflows
You need Git-like branching and merging, distributed, but miss security, huge project support, scalability. Check this.
Perforce migration
You need the industrial-strength but also modern version control. Then check how to migrate .
Implement DevOps
You can implement a true DevOps cycle with Plastic SCM and Bamboo/TeamCity/Jenkins. Learn more.
When the going gets tough
The tough get going
Every version control can create a few branches and perform a few merges. Very few can do it at enterprise scale. Don't take version control for granted. It is the operating system of software development.
What is Enterprise Edition
Plastic SCM Enterprise Edition is a full version control stack to handle the heavy load required by teams and corporations to implement their collaboration infrastructure and processes.
Version control is the single source of truth for DevOps. Continuous Integration systems, automated testing frameworks, Continuous Delivery software, issue trackers and project management tools, they all rely on the underlying version control to obtain data.
Under heavy-load scenarios many well-known version control crumble. It is easy to create a few branches on a small codebase. But it is a different game to branch in miliseconds a codebase of +700k files in a server attending thousands of concurrent users.
If you ever experienced that pain, then Enterprise Edition is for you.
Besides, Enterprise Edition is a full stack. It means it is not just an isolated service, it comes with the GUIs, diff and merge tools, admin tools and everything your company needs to successfully implement version control, in a single package provided by a single vendor. Every single piece engineered with high productivity in mind.
Here are some real situations that Enterprise Edition handles in those companies:
Serve thousands of repos
Serving +6000 repositories on a single corporate server to manage multiple project portfolios, including nested repository hierarchies. Attending fast +1500 developers across different geographies.
+3000 developers on a single server
Corporation with +3000 developers worldwide accessing a network of servers in centralized, distributed and multi-site scenarios.
Perform under heavy load
Heavy loaded server in video game companies performing fast under +1 million requests per hour downloading and storing GBs of data on a daily basis. Repositories served are in the +4TB range.
Branch huge codebases
Company with +500 developers contributing to a single codebase with +700k files on the working copy using task branches. This means hundreds of new branches created daily on the big codebase tree with zero impact in performance (branches are created in milliseconds independently of size).
Orchestrate DevOps
Teams using mergebots to orchestrate DevOps and avoiding broken builds. Plastic mergebots implement a consistent way to test merged code before the merge is confirmed, which avoids broken builds like no other CI/CD system can. mergebots support Jenkins, Bamboo, TeamCity and an always growing list of CD solutions.
Locking & branching
Artists in a game team taking advantage of a natural workflow with Gluon and file locking while programmers make extensive use of branching, merging and distributed workflows. All in the same repo.
Reduce manual conflicts
Teams reducing manual intervention in branch merges up to a 30% thanks to the built-in semanticmerge technology in mergebots. Lots of context switching is avoided with a positive impact in individual productivity.