Plastic SCM - Detailed Review
Collaboration Tools
Plastic SCM - Detailed Review Contents
Add a header to begin generating the table of contents
Plastic SCM - Product Overview
Primary Function
Plastic SCM is a version control system that helps teams manage their software development projects efficiently. It supports both distributed and centralized version control, allowing it to work on-premises or in the cloud. The system is built to handle large repositories and big binaries, making it suitable for projects of various sizes.Target Audience
Plastic SCM is primarily used by companies in the Information Technology and Services, Computer Games, Computer Software, and Higher Education sectors. The user base includes small, medium, and large enterprises, with a significant presence in the United States, Spain, the United Kingdom, and Canada.Key Features
Branching and Merging
Plastic SCM offers advanced branching and merging capabilities, similar to Git but with additional features. It includes a powerful merge engine that handles large case volumes and promotes parallel development and refactoring. The system also provides a visual Branch Explorer, allowing users to customize and navigate branches easily.Visualization
The software includes a 2D Version Tree and other visual tools that help users understand the branching and merging workflow. This visualization makes it easier to manage and track changes within the project.Integration and Scalability
Plastic SCM integrates with various Continuous Integration (CI) systems such as Jenkins, Bamboo, and TeamCity. It also supports Git synchronization, allowing teams to work with large repositories and scale as needed.Security
The system has robust security features, including authentication via username/password, LDAP, Active Directory, and NIS . It uses access control lists (ACLs) to manage access to repositories, files, and revisions, ensuring secure and controlled access to project assets.Flexibility and Ease of Use
Plastic SCM is flexible in terms of repository management, allowing teams to create small or large repositories as needed. It supports fast-export/fast-import interchange formats for easy data migration from other SCM tools. The system also provides a user-friendly interface with GUI tools for Linux, macOS, Windows, and a web interface, making it easy for developers to manage their workspaces and track changes. Overall, Plastic SCM is a versatile and powerful tool that enhances team collaboration, improves version control, and supports a wide range of development practices such as DevOps, Agile, and Kanban. Plastic SCM - User Interface and Experience
User Interface Overview
The user interface of Plastic SCM is crafted to be intuitive and powerful, making it a user-friendly tool in the collaboration tools category.Graphical User Interface (GUI)
The Plastic SCM GUI is accessible by executing the `plastic` or `plastic.exe` command from a command processor. This interface is structured around the concept of workspaces, where you can have multiple workspaces but work with one active workspace at a time. This active workspace is akin to the current working directory in a command processor.Main GUI Window
The main GUI window is divided into several key areas:- Work Context: This is the central region that displays information related to the active workspace. It includes multiple tabbed windows, known as views, which can be opened or switched using buttons in the left panel. The GUI preserves the state of the work context even when you switch between different workspaces.
Views and Customization
While the GUI offers a range of views, users have noted some limitations in customization. For example, there is a desire for more flexibility in selecting which columns are visible in each view, such as displaying attributes and labels in the Changesets view.Help System and UX
Plastic SCM includes a built-in help system that guides users through the interface. This system features a mascot, an owl, which provides tips and assistance to help users discover new features and resolve potential issues. The help system is integrated into all views, enhancing the overall user experience.User Experience
Users generally praise the visual aspect and ease of use of Plastic SCM. The branching and merging processes are particularly highlighted as being easy to manage. However, some minor UX issues have been reported, such as slow scrolling in certain views and limitations in mouse wheel functionality, especially in the Branch Explorer.Web User Interface (WebUI)
In addition to the GUI, Plastic SCM also offers a Web User Interface (WebUI) that allows users to browse repositories online. This WebUI features repository views, item views, branch browsing, and the ability to run code reviews online. It also includes a statistics module for analyzing repository data. The WebUI is user-friendly and accessible even for those without deep knowledge of the system.Ease of Use
Overall, Plastic SCM is praised for its ease of use. The interface is visually appealing, and the tools are powerful yet straightforward. The help system and smart guidance features contribute to a smooth learning curve, making it easier for new users to get started. However, some users have suggested improvements, such as better customization options and improved scrolling functionality, to further enhance the user experience.Conclusion
In summary, Plastic SCM’s user interface is well-structured, easy to use, and supported by a helpful guidance system. While there are some minor issues and areas for improvement, the overall user experience is positive, making it a viable choice for collaboration and version control. Plastic SCM - Key Features and Functionality
Plastic SCM Overview
Plastic SCM is a comprehensive version control system that offers a range of features to support collaborative software development, but it does not specifically fall under the category of AI-driven products. Here are the main features and functionalities of Plastic SCM:Version Control and Repository Management
Plastic SCM manages any number of repositories, each storing the entire history of a particular directory tree. Each item in the tree can have multiple revisions, and these revisions can be organized into named branches. This allows for parallel development and efficient management of different versions of the codebase.Workspaces
Users work within a workspace, which is a directory tree on their computer with a two-way data path to a repository. The `Update` command loads the latest revisions from the repository into the workspace, and the `Checkin` command sends changes back to the repository. This workflow is similar to other version control systems like Subversion and Git.Branching and Merging
Plastic SCM supports powerful branching and merging capabilities. Branches make it easy to configure a workspace to work on a specific branch, and the system provides visualization tools to manage these branches effectively. This feature is particularly useful for task branches and trunk-based development, integrating well with Agile, DevOps, and Kanban practices.Labels
Labels are user-defined names attached to changesets, making it easier to mark and recall specific versions of the codebase. Labels can be quickly created, applied, and managed, and they do not require marking every revision of the items in the workspace. This feature is useful for tracking releases and milestones.Security and Access Control
Plastic SCM has robust security features, including authentication and access control lists (ACLs). Users must be authenticated to access the system, and ACLs can grant or deny access to various entities, from entire installations to individual files or revisions. The system supports network-based authentication systems like NIS , LDAP, or Active Directory.Integration with CI Systems
Plastic SCM integrates with Continuous Integration (CI) systems such as Jenkins, Bamboo, and TeamCity. This integration allows for automated builds, merges, and labeling, enhancing the overall development and deployment process. The integration with TeamCity, for example, enables full-blown automation from source control to CI, facilitating faster and better software delivery.GUI and User Interface
The Plastic SCM graphical user interface (GUI) is user-friendly and powerful, covering all client functionality. It includes features like multiple workspaces, tabbed views, and a help system that guides users through the interface. The GUI preserves the state of the work context even when switching between workspaces.Import and Export
Plastic SCM supports the fast-export/fast-import interchange format, allowing data to be imported from other version control systems. This feature is useful for migrating projects from other SCM tools into Plastic SCM.AI Integration
There is no specific information available on the integration of Artificial Intelligence (AI) into Plastic SCM. The features and functionalities of Plastic SCM are focused on version control, branching, merging, and integration with CI systems, but it does not include AI-driven capabilities. If you are looking for AI applications, they are more relevant in other contexts, such as the plastic industry itself, where AI is used for quality control, predictive maintenance, supply chain optimization, and more. Plastic SCM - Performance and Accuracy
Performance
Plastic SCM is known for its strong performance, particularly under heavy loads. In a scalability test comparing Plastic SCM 3.0 against Subversion (SVN) 1.5.7 and Perforce 2009.2, Plastic SCM demonstrated superior handling of concurrent clients. The test involved a single server and 100 concurrent clients, and Plastic SCM outperformed the other systems, especially in scenarios involving trunk development and branching. Plastic SCM’s use of a SQL Server backend contributes to its ability to manage large workloads efficiently. It can handle repositories with thousands of files and branches without significant performance degradation, which is a notable advantage over other version control systems like Git or Perforce.Handling Large Repositories and Branching
Plastic SCM is optimized for handling large repositories and extensive branching. It can manage thousands of branches and automate merges that other systems struggle with. This capability makes it particularly suitable for projects that require frequent branching and merging, such as those following Agile or DevOps practices.Network Performance
In some cases, users have reported that Plastic SCM may not utilize the full network bandwidth available. For example, a test on a gigabit LAN showed that Plastic SCM achieved only 10-25% of the total network speed when checking in large files. However, this could be due to various factors such as the specific setup and the database backend used.Accuracy and Reliability
Plastic SCM is built with a focus on accuracy and reliability. It provides advanced diff and merge tools, including semantic diff and merge capabilities, which are unique in the industry. This ensures that changes are accurately tracked and merged, reducing the likelihood of conflicts and errors.Limitations and Areas for Improvement
While Plastic SCM performs well in many areas, there are some limitations and potential areas for improvement:Repository Size and Network Utilization
As mentioned, Plastic SCM may not always utilize the full network bandwidth, which could be a point of improvement, especially for large file transfers.Server and Client Compatibility
There have been issues reported with running SVN on Windows servers, which led to crashes and performance issues. However, Plastic SCM itself performs well on both Windows and Linux servers.Realistic Test Scenarios
Some users have suggested that the test scenarios could be more realistic, such as using larger repositories and more varied file types to better reflect real-world usage.Conclusion
Plastic SCM stands out for its performance, particularly in handling heavy loads and extensive branching. Its ability to manage large repositories and provide advanced diff and merge tools makes it a reliable choice for collaborative development projects. However, there are areas where improvements could be made, such as optimizing network utilization and ensuring compatibility across different server and client configurations. Overall, Plastic SCM is a strong contender in the version control and collaboration tools category. Plastic SCM - Pricing and Plans
Plastic SCM Pricing Structure
Plastic SCM offers a varied pricing structure to cater to different user needs, from individual developers to large enterprises. Here’s a breakdown of the various plans and their features:
Free Plans
Personal Edition
- This plan is free and intended for hobbyists and individuals.
- It includes all the basic version control features, making it suitable for solo developers or small personal projects.
- There are no user limits, but it is meant for non-commercial use.
Community Edition
- Also free, this edition is specifically for non-profit organizations.
- It offers similar features to the Personal Edition but is restricted to non-profit use.
- It includes 5 GB of cloud storage and support for up to 15 users.
Paid Plans
Cloud Edition
- Priced at $6.95/month (or $7/month in some sources), this plan is ideal for teams that need a cloud server.
- It includes cloud project hosting, GitServer capabilities, and optional local repository clones.
- This plan supports up to 15 users and includes 5 GB of cloud storage.
Team Edition
- This plan costs $9.95/month.
- It includes all the features of the Cloud Edition plus additional capabilities such as remote connection, on-premises server support, and integration with Postgres and LDAP/Active Directory.
- It is designed for teams that need more advanced features and better scalability.
Enterprise Edition
- Priced at $23.25/user/month or a one-time payment of $595.00/user.
- This plan includes all the features of the Team Edition plus additional enterprise-level features such as highly scalable on-premises servers, proxy servers, and optimized backend for large files and high latency networks.
- It also offers advanced access control, semantic diff, and refactor analysis.
Additional Considerations
- Educational Discounts: Codice Software provides substantial discounts for educational institutions.
- Volume Pricing: Corporate or volume enterprise pricing is also available upon contacting the sales team.
- Free Trial: A free trial is available for users to test the features before committing to a paid plan.
Each plan is designed to meet the specific needs of different types of users, from solo developers to large enterprise teams, ensuring that you can choose the plan that best fits your requirements and budget.
Plastic SCM - Integration and Compatibility
Integration with IDEs
Eclipse IDE
Plastic SCM integrates seamlessly with several popular Integrated Development Environments (IDEs). For instance, it has a complete integration plug-in for the Eclipse IDE, supporting Eclipse versions 3.1 and higher. This integration covers common operations such as creating workspaces, checking out and checking in code, and managing branches and merges. Additionally, Plastic SCM supports Mylyn integration in Eclipse, allowing developers to link branches or changesets with tasks directly within the IDE.JetBrains IDEs
For JetBrains’ IDEs, Plastic SCM is fully compatible with all 12 IntelliJ Platform products, including IntelliJ IDEA, PyCharm, PhpStorm, WebStorm, and others. This integration allows developers to access Plastic SCM functionality directly from their preferred JetBrains interface, ensuring a smooth development experience.Compatibility with CI Systems
Plastic SCM is compatible with various Continuous Integration (CI) systems. It integrates out-of-the-box with Jenkins, Bamboo, and TeamCity, and its API allows for integration with virtually any CI system. This flexibility makes it easy to automate builds, merges, and other CI-related tasks.Git Compatibility
One of the standout features of Plastic SCM is its GitSync capability, which allows it to work seamlessly with Git repositories. GitSync enables developers to use either Plastic SCM or Git on their workstations, converting Git repositories into Plastic SCM format and vice versa. This feature ensures that branches and commits are accurately mirrored between the two systems, making it ideal for teams that need to work with both version control systems.Platform Support
Plastic SCM supports a wide range of platforms, including Windows, macOS, and Linux. It offers GUI tools for each of these operating systems, as well as command-line tools and a web interface. This broad support ensures that developers can use Plastic SCM regardless of their preferred operating system or development environment.Additional Tools and Features
Plastic SCM also includes advanced tools such as SemanticMerge, which performs diffs and merges based on code structure rather than text. This tool, introduced in version 5.0, enhances the merging process, especially for large and complex codebases. Other features include path-based security, client changelists, and WAN-optimized data transfer, making it a comprehensive version control solution.Conclusion
In summary, Plastic SCM offers strong integration with various IDEs, CI systems, and platforms, along with advanced features that enhance the version control experience. Its compatibility and flexibility make it a valuable tool for development teams across different environments. Plastic SCM - Customer Support and Resources
Customer Support Options
Plastic SCM offers a comprehensive range of customer support options and additional resources to ensure users can effectively utilize their version control system.Support Tickets and Email
Users can create a support ticket directly through the Plastic SCM website or by emailing the support team at `devops-vcs-support@unity3d.com`. This allows for direct communication with the support team to address any issues or questions.Community Forum
Plastic SCM has a community forum integrated with the Unity forum, where users can ask questions, share experiences, and submit bugs. This community-driven platform facilitates peer-to-peer support and knowledge sharing.Documentation and Guides
Extensive documentation is available, including an Administrator’s Guide that covers installation, creating repositories, workspaces, and backups. This guide is accessible both through the command line interface and the graphical user interface’s Help menu.Training and Consulting Services
For users who need more in-depth assistance, Plastic SCM offers training and consulting services. These services can be customized to meet the specific needs of the user and are available for a fee. Contacting the support team can provide more information on these services.Remote Support Connection
In cases where issues are more complex, Plastic SCM’s support engineers can connect to the user’s machine to resolve problems. This remote support connection is part of the support package and ensures that users can get help even with more challenging issues.Software Upgrades and Hotfixes
Users are entitled to software upgrades, including major and minor releases, as well as priority for code hotfixes from the development team. This ensures that the system remains up-to-date and any critical issues are addressed promptly.Licensing and Evaluation
For those evaluating Plastic SCM for commercial use, there is an option to download an evaluation copy for 30 days for up to five users. This allows potential users to test the system before committing to a purchase. Additionally, the licensing terms are flexible, with options for annual or monthly subscriptions, and support for various payment methods.Conclusion
By providing these support options and resources, Plastic SCM ensures that users have the help they need to effectively manage their version control and development processes. Plastic SCM - Pros and Cons
Advantages
Flexible Workflow
Plastic SCM supports both distributed and centralized version control, allowing teams to combine these workflows in creative ways to suit their needs. This flexibility is particularly beneficial for game development and other centralized efforts.
Cloud and On-Premises Support
Plastic SCM can be hosted on the cloud or on-premises, offering teams the flexibility to choose the deployment method that best fits their requirements. This also includes support for various database management systems like Firebird, Postgres, and SQLite.
Advanced Branching and Merging
Plastic SCM features top-notch branching and merging capabilities, similar to Git, but with additional strengths such as handling large binaries and a powerful merge engine. This engine is praised for its speed and reliability in resolving complex merge cases.
Visual Branch Explorer
The tool provides a visual branch explorer, which makes it easier to manage branches and track changesets. Users can customize legends and work with a vertical layout, enhancing the efficiency of branch management.
Semantic Diff and Refactor Analysis
Plastic SCM includes advanced diff tools, such as semantic diff and refactor analysis, which help in tracking changes like deleted lines, swapped methods, and moved classes across multiple files.
Easy Hosting and Maintenance
By offering cloud-hosted options, Plastic SCM simplifies the process of hosting and maintaining repositories, allowing teams to focus solely on development.
Active Maintenance and Updates
The software is actively maintained and updated, with regular improvements and new features added, which is a positive sign for its ongoing support and development.
Disadvantages
Scalability Issues
One of the significant drawbacks of Plastic SCM is its scalability. While it works well for smaller teams and repositories, its performance declines with larger setups, leading to major issues. This makes it less suitable for large-scale projects compared to alternatives like Perforce Helix Core.
Commit Restrictions
Plastic SCM uses a per-changeset model that requires the entire workspace to be up to date before allowing a commit. This can introduce unnecessary delays and restrictions, particularly for developers who need to commit changes to specific files without updating the entire project.
Performance Comparison
In performance tests, Plastic SCM may not compare favorably to other systems like Perforce Helix Core, especially in larger scenarios. For example, a “medium” test scenario for Plastic SCM would be considered “small” or “extra-small” for Helix Core, and Helix Core has shown better performance on Linux environments.
User Interface and Workflow Adjustments
Some users might find the need to adjust to a new workflow and interface, especially if they are accustomed to other version control systems. For instance, the visual branch explorer, while beneficial, may require some time to get used to.
In summary, Plastic SCM offers a range of powerful features and flexibility that can be highly beneficial for teams, especially those in game development or similar centralized workflows. However, its scalability limitations and specific commit restrictions are important considerations that need to be weighed against the needs of the project.
Plastic SCM - Comparison with Competitors
Version Control Capabilities
Plastic SCM is a full version control stack that offers both centralized and decentralized models, similar to Perforce and Git. It is particularly known for its branching and merging capabilities, including task branches, diff tools, and 3-way merge tools. This makes it suitable for complex integration scenarios and supports various development workflows, including those for artists and designers.User Interface and Integration
Plastic SCM boasts an intuitive interface, especially with its GUI tool Glueon, which is user-friendly for artists and designers. It also integrates seamlessly with Unity, providing a cohesive environment for Unity developers. However, this integration might not be as beneficial for teams not using Unity.CI/CD Integration
Plastic SCM can integrate with various Continuous Integration/Continuous Deployment (CI/CD) systems, including Jenkins, Bamboo, and TeamCity, thanks to its API. This allows for automated builds, merges, and labeling, making it a versatile tool for DevOps practices.Alternatives and Comparisons
Perforce Helix Core
Perforce Helix Core is a strong competitor that also offers centralized and decentralized version control. While Plastic SCM has a more modern feel and better support for binary files, Helix Core excels in handling large and complex codebases with its Stream Graph feature, which simplifies the merge process and code organization. Helix Core also provides a time-lapse view of code history, which Plastic SCM lacks.Anchorpoint
Anchorpoint is another alternative built on Git, offering standard Git features along with additional collaboration tools like file locking. It stands out with its ability to display thumbnails for various file formats, enhancing the visual representation of changes. Anchorpoint also functions as an asset management tool, allowing users to tag, annotate, and approve assets. This makes it a good choice for teams already familiar with Git and needing advanced asset management.AI-Driven Collaboration Tools
While Plastic SCM itself is not primarily an AI-driven collaboration tool, it can be used in conjunction with other tools that offer AI-enhanced features. For example, integrating Plastic SCM with project management tools like Asana, Trello, or ClickUp can add AI-driven capabilities such as task prioritization, automated workflows, and predictive analytics to your workflow.Summary
Plastic SCM is a powerful version control tool with strong branching and merging capabilities, a user-friendly interface, and good integration with CI/CD systems. However, it may not offer the same level of code history visualization or complex codebase handling as Perforce Helix Core. For teams needing more AI-driven collaboration features, integrating Plastic SCM with other project management tools can provide the necessary enhancements. If you are already invested in the Git ecosystem, Anchorpoint could be a more suitable alternative. Plastic SCM - Frequently Asked Questions
Frequently Asked Questions about Plastic SCM
Q: What are the key features of Plastic SCM?
Plastic SCM offers several key features that make it a versatile version control system. It supports both distributed and centralized version control, allowing it to work on-premises or in the cloud. It has top-notch branching and merging capabilities, similar to Git, but with the ability to handle larger files and binaries. The software also includes a powerful merge engine, a visual branch explorer, and integration with Git services.Q: How does Plastic SCM handle security?
Plastic SCM has robust security features, including user authentication and access control lists (ACLs). Users must be authenticated under a particular username to access the system, and you can configure it to use network-based authentication systems like NIS , LDAP, or Active Directory. The ACL system allows for fine-grained control over access to repositories, files, and even individual revisions.Q: Can Plastic SCM handle large repositories and big files?
Yes, Plastic SCM is capable of handling large repositories and big files. There are no size limits, and the system can scale as needed. It can manage big binaries, and the limit is essentially what your RAM can handle. This makes it suitable for projects that involve large files and extensive development histories.Q: How do I switch from Collaborate to Plastic SCM in Unity?
To switch from Collaborate to Plastic SCM in Unity, you need to open your Project Settings, go to Services > Collaborate, and switch off Collaborate. Then, you can start using Plastic SCM by following the migration steps provided by the Collaborate migration tool. This involves downloading and installing the Plastic SCM Cloud Client, logging in, and setting up your workspace.Q: What is the Visual Branch Explorer in Plastic SCM?
The Visual Branch Explorer in Plastic SCM is a feature that provides a graphical representation of your branches and changesets, rather than the standard text-based tree explorer. This allows you to quickly identify which changeset you are working with and customize your legends for swift navigation. You can also switch to a vertical layout if preferred.Q: How does Plastic SCM support parallel development?
Plastic SCM supports parallel development through its branching system. Each branch has a designated starting changeset, and you can easily configure your workspace to work on a specific branch. This system avoids the complexity of other SCM systems and makes it simple to manage multiple branches and revisions.Q: Can I use Plastic SCM with different database management systems?
Yes, Plastic SCM supports a variety of database management systems, including Firebird, Postgres, and SQLite. This flexibility allows teams to choose the database system that best fits their needs and infrastructure.Q: How do I get support for Plastic SCM?
For support, you can use the Plastic SCM forum to ask questions, share experiences, and submit bugs. Additionally, you can create a support ticket or email the support team directly at devops-vcs-support@unity3d.com.Q: What are labels in Plastic SCM, and how are they used?
Labels in Plastic SCM are user-defined names that can be attached to a changeset. This makes it easier to remember specific versions of your project rather than using changeset numbers. Labels are quick to create, apply, and manage, and you can even change a label’s name if needed.Q: Can I use Plastic SCM with multiple repositories?
Yes, Plastic SCM can handle any number of repositories, each storing the entire history of a particular directory tree. You can assemble multiple repositories into the desired tree structure using Xlinks, which allows for flexibility in managing your project’s repository structure.Q: How do I set up my workspace in Plastic SCM?
To set up your workspace in Plastic SCM, you need to create a workspace and use the `Update` command to load source files into it. The Plastic SCM GUI makes it easy to keep track of your workspaces, switch between them, and create new ones. For Unity projects, you can follow the specific steps outlined in the migration tool to set up your workspace using either the Developer Workflow or the Gluon Workflow.