#1 most frequent
United States of America
42.9%66 installations of 154
What is Plastic, now part of Unity DevOps?
Plastic was a version control system for facilitating branching, diffing and merging. It was acquired by Unity, and its features are part of Unity DevOps. The application is no longer available for sale.
Categories & Use Cases
Media
1 / 6
Who Buys & Uses Plastic, now part of Unity DevOps
#2 most frequent
United Kingdom of Great Britain and Northern Ireland
9.1%14 installations of 154
#3 most frequent
India
5.8%9 installations of 154
Great tool for Game Development - already integrated in Unity
Use Cases and Deployment Scope
We use it as a tool inside Unity. It's great to keep things organized as an alternative to github/gitlab/bitbucket. Moreover, for huge projects with lots of assets, scripts in the range of dozens, code trees ranging 5k+, it's a very reliable and already integrated tool in our workflow.
Pros
- Version Control
- Organizing Workflow
- Transparency
Cons
- Interface
- Documentation
- Learning curve
- Unity integration
Most Important Features
- Gluon
- Cloud Server
- Branching
- Security
- Unity single click usage
Return on Investment
- Easy to use
- Cheap
- Better than git for us
- Artists love it
Alternatives Considered
GitHub, Bitbucket and Sourcetree
Other Software Used
Slack, Miro, Sourcetree
Great control version tool for software development
Use Cases and Deployment Scope
My team uses Plastic SCM for version control, to collaborate our SaaS project within other team members working on the same software. We use it to store our unity projects on cloud. So Plastic SCM helps us to control every branch. Besides the features, it has a nice and friendly GUI.
Pros
- Version Control
- File Locking
- Branch Resolution
Cons
- Complex
- Could be easier on integrations
- Lot of menus
Most Important Features
- Version Control
- Easy Merging
- UI
Return on Investment
- Saves time
- Processes get less complicated
Make workflow flexible wit Plastic SCM
Use Cases and Deployment Scope
We are developing a big, distributed product for an aviation giant. So the business is complex and so is the technical implementation. A team of 25 people are working on it. So a distributed collaboration is required for systematic development. Plastic SCM is providing us the same environment which is most suitable for our development requirement. It supports the version control for our project and the branching and merging solution for the continuous and simultaneous development. In this way team is able to leverage the best efficiency.
Pros
- Branching
- Merging
- binary freeze or locking
- decentralized behavior
- Efficient for large projects as well, really fast and quick
- Versioning and controlling the repositories
Cons
- No administrative tool, so a lot of manual work need to be done
- Quite often the workspace for Plastic SCM disappears and its weird
- Its not easy to use initially as it requires a knowledge and some efforts
- Its not preferable for the small projects as to set up and use takes a lot of efforts
Most Important Features
- Best for distributed systems
- It goes very well with the giant repos
- Functionality to lock/freeze files/binaries to avoid the merging conflicts and issues
- branching and merging
- graphical visualization of repos to get better understanding and insights of branching
Return on Investment
- Its not good for smaller projects
- Its a bit complex to understand at initial stages so requires some effort to learn tool
- but if project is big and a lot of people are contributing simultaneously then in that case it multiplies the power of team
