Plastic SCM Enterprise & Team & Cloud Edition v18.104.22.16866 (27 May 2020) + CRACK
What is Plastic SCM?
Plastic SCM is a distributed version control, but can work centralized too. It is excellent with branching and merging, can deal with huge projects and big binary assets natively, and it comes with GUIs and tools to make everything simpler.
Plastic SCM is the operating system of software development. It can solve problems efficiently and silently, or it can create more.
Big files, huge projects, Unity and Unreal? Tired of Perforce and can’t go to Git? We got you covered
Key Features of Plastic SCM
- Branching & Merging: Good branching and merging is key for "task driven development" , feature branches, and good release management. Using Plastic, you'll branch fast even with huge code bases.
You'll handle merge cases that no other tool can deal with.
You'll be able to diff refactored code with the new built-in semantic diff plus the "analyze refactors" feature. It can find refactored code across files for C#/Vb.net, Java and C.
The built-in 3-way merge tool Xdiff/Xmerge lets you resolve even the most complex merge conflicts since it features language-agnostic refactoring support. Plastic includes our SemanticMerge product. This means that you get the extra power of code-aware merges if you need full semantic merge capabilities.
Since an image is worth a thousand words, you can visualize the merges using the Branch Explorer .
Item merge tracking helps you to understand merges when running diffs, annotates and displaying the 2D version history of a file.
- Distributed, multisite and centralized
- Fully distributed
Using Plastic, a developer can have a clone of the repository on their local machine and checkin, branch and merge without connection to the main server. This is what fully distributed is all about.
The benefit is clear in terms of speed, enabling developers to work from home without suffering slow VPNs or being hit by a network issue. Developers can pull and push changes to any other Plastic server (depending on the permissions) anytime. In extreme distributed environments, developers wouldn't even use a central server. However, in practice, a central place will be used as a rendezvous point.
- Graphical User Interface and Visualizations: Plastic is much more than a scalable core and a great merge engine. Everything we do has the end user in mind and making things simple and visual is key for us.
- GUI: Plastic allows you to perform every version control operation from the GUI, which is pretty easy to learn. User experience is our most important goal.
- Branch Explorer: The Branch Explorer is the core feature of the GUI. It is an interactive graphic that renders the evolution of the repository. From the Branch Explorer view you can branch, merge, diff, push and pull and switch to different branches. If there is only a single feature that makes Plastic worth it, this is the Branch Explorer. Find out more here.
- Built-in Code review: Plastic includes an integrated code review system. You can create reviews from changesets and branches, add comments to lines and assign the review to a developer to check it. Reviews are replicated between repos with their branches. Find more in the GUI guide.
- Version tree 2D: You can display the history of a file visually using a 2D version tree. Then you can follow how it was branched and merged and run diffs from the diagram. Check the GUI guide for details.
- Annotate/Blame: This view shows who wrote every line of and file. Each line is annotated with the date, the changeset and the branch. Additionally, the annotate view displays the line age and it can summarize the file age and main contributors.
- Built-in side by side diff: Plastic includes a built-in diff tool, Xdiff, which can be invoked as a separate tool but it is also used inside the GUI to show side by side differences. It has the ability to track moved text (even when it has been modified). You can find this in Plastic, inside the pending changes view, diffing changesets or branches or running code reviews.
- Built-in 3-way merge with refactor detection: Plastic comes with our SemanticMerge product. This means if you are merging C#, Java, VB.NET, or any other language supported by SemanticMerge, you get the extra power of code-aware merges.
Plastic also includes its own 3-way merge tool called Xmerge. Besides being a regular merge tool, it can track and merge moved code fragments. Plastic also lets you plug in any other 3-way merge tool like Araxis, BeyondCompare, and many others.
- Diff window - branch, changeset and label diff: Each time you need to diff branches, changesets or labels, you'll use the Diff Window . It is a very complete interface that shows changed, added, deleted, moved and files that have been merged in the changesets, labels or branches you're diffing.
- Image diff: Plastic includes an image diff tool, able to compare two revisions of the same graphics file. The file can be in a variety of file formats (especially if you have ImageMagick installed). This tool can show images side by side, do an "onion skin" preview, calculate differences, do a "swipe" and diff the image properties in text format. More details in the GUI guide.
- Image preview in the workspace explorer: When you browse the files in your workspace, you can preview the image files and read the extended properties stored on it. Plastic can be configured to use ImageMagick to generate previews of hundreds of different formats. You can even write your own custom previewer to support custom file formats (quite common in game development). It will also be used to diff image files.
- Semantic Version Control: We believe that version control holds a unique position to give developers extra tools for the job. It stores all the evolution of the project and hence information that, correctly mined, can help in daily operations. That's why we created SemanticMerge first, and then we applied the technology to the version control itself...
- Analyze Refactors: You can now diff a branch or a changeset and easily diff methods even when they were moved between files and later modified. Plastic analyzes the diffs to find refactors and eases diffing and reviewing the code.
This feature is also known as "multi-file" semantic diff and is included in Plastic for C#, Java, Vb.net and C.
- Built-in Semantic Diff: Each time you diff a branch, a changeset, or your local pending changes, you can activate "semantic diff". Plastic will parse the files and calculate the differences semantically, method by method, finding the right diffs even when a method was moved, renamed or was heavily modified.
- Semantic History: 90% of the time that you go through the history of a file you are looking for the history of a given method or function. Semantic History lets you select a method and find how it was modified through the history of the file. It parses the code and it can find the method even when it has been moved, renamed or heavily modified throughout its history.
You can use this feature both from the GUI and the Visual Studio Package. It can track methods, properties, constructors, members and more.
- Next steps: It all started with Xdiff/Xmerge, able to track moved text (language independent) and then continued with SemanticMerge and Analyze Refactors. Our next goals are:
- Semantic Repo History: to track methods moved across files.
- Multifile SemanticMerge: the *real* Semantic that will be able to merge methods that were refactored across files too.
- Semantic blame/annotate: to give the programmer extended info of each line of code and method while they type in Visual Studio, warning them about code that has a long and complex history behind it, bugs and more.
- Performance & scalability: Checkin, update and merge as fast as possible. Handle hundreds of concurrent developers using the same server. Manage huge files. These are the things you can do with Plastic.
- Scalability under heavy load: Check how Plastic performs when 300 bots checkin at 2000 checkins per minute. Scaling up on centralized setups is key for many teams, and core to Plastic.
- Improved blob storage: Big blobs (configurable size) can be stored in the filesystem instead of the database for storage optimization and performance.
- Single port operation & binary protocol: All data transfer between the Plastic client and server uses an optimized binary protocol that compresses all metadata to speed up communications. All connections between clients and servers happen through a single TCP port (several can be configured if needed, but only one is needed by default) which makes the server very easy to configure and secure.
- Proxy server: Although Plastic is a full featured DVCS capable of replication, we also provide a proxy server (or cache server) to reduce data traffic to the central server. We don't recommend this setup for multi-sites but for high demand, heavy load scenarios where reducing data traffic on certain network segments can greatly improve overall network performance.Check out this blogpost for more details.
- Fast-update: A standard Plastic update (download files to the workspace) walks the entire directory tree looking for changes. It is very efficient, but teams with very large codebases (greater than 500,000 files) can end up experiencing slower IO and slower updates. That's why fast-update just applies differences on disk, avoiding the full scan. Going from cset 3000 to 3014? It just calculates the differences and applies them on disk, reducing disk IO and improving speed.
- Archiving – External storage: You can extract revisions of large files from the database to be stored in secondary storage. Once archived, the revisions can be accessed in two ways:
- Transparently for the users when the server is setup to find archived revisions in external storage.
- Prompting the user to insert the right media on their workstation (useful if your team uses an asset library with different media)
- WAN optimized data transfer: Teams with servers in different continents replicate branches through high bandwidth but high latency networks. The "WAN network channel" typically improves data transfer speed by 3 with 200ms latencies compared to regular TCP. This is very useful for companies replicating big files between different teams across the globe. Find out more here.
- Multi-thread checkin and update: Checkin and update can be configured to use multiple threads. This way, data compression and decompression will run in parallel with network and disk IO operations, greatly improving overall operation performance as you can see here.
- Configurable database backends: Plastic stores all data and metadata in standard database backends. The default installer uses SQLite on Windows, Linux and Mac. You can easily configure it to use SQL Server (including Express), MySQL (and MariaDB), PostgreSQL or Firebird (both embedded and server). This flexibility allows you to run a tiny and extremely efficient Plastic server using SQLite on your laptop or take advantage of a corporate server with SQL Server or MySQL.
SysDBAs have the flexibility to setup clusters and apply optimizations since Plastic uses standard SQL structures. Backup is done with standard tools too. Blobs are stored in 4Mb chunks, compressed, and there's an option to store them in the filesystem (or SQL Server FILESTREAM fields).
- Component oriented development: You can use and develop shared components in Plastic using Xlinks and submodules.
Cross-links are the way to link together different repositories, potentially creating a hierarchy of components shared among different projects. An Xlink is a special directory entry that points to a given changeset on a different repository (potentially on a different server). The contents of the Xlink will be transparently downloaded to the user workspace. There are read-only Xlinks which are meant to handle dependencies that rarely change, and writable Xlinks to handle parallel development across a codebase made of several repositories. Branching and merging is handled by Plastic on writable Xlinks.Check out the Xlinks guide.
By default, Plastic stores every repository in a different database. Submodules allow admins to store several repositories inside the same physical database which is useful both for database administration and to create repository namespaces in organizations with hundreds of repositories. Submodule repository names look like "graphics/opengl" and "graphics/directx" instead of just the single name given to a repo.
- Productivity: There are several features that help you on a daily basis when you're working with Plastic:
- Transparent SCM: You can program using your favorite IDE/editor and Plastic will detect the changes you've done. You change a file and Plastic detects it. You move a file, a directory and Plastic also detects the move, perfectly tracking it even when the file was changed. This is what we call transparent scm and basically allows you to forget about the version control until you must checkin and then Plastic will do its part, detecting even complex changes. Find out more here.
- Client changelists: This feature helps you to organize the pending changes (to be checked-in) in your workspace with user defined categories. One of the goals is to make the Perforce users feel at home. Check the guide for more info.
- Shelve (a.k.a. stash): You can "shelve" changes in Plastic and keep them saved in the server (not checkedin) until you apply them later. You can shelve several files together and give them a description. They'll be applied using merge, so it is a good way to apply changes to a different branch. Find out more in the GUI guide.
- Exclusive checkout (locking): There are files that can't be easily merged or even merged at all, like images, animations, simulation data, 3D files and many more. Using Plastic, you'll be able to exclusively checkout (lock) these files to avoid concurrent modification. This is key for many industries, like game development.
- Attributes: You can create your own metadata in the form of name/value pairs, attaching them to any object in the repository. This enables you to create sophisticated reports, using data retrieved by SQL queries. Check out the Find guide. Later, you'll be able to see the attributes in the GUI in places like the branches list, the Branch Explorer and more.
- Transformable workspaces: Sometimes you need to apply some transformations to your working copy that you don't want to checkin. For instance, you need the "/extlibs/includes" to show up inside "/includes/extlibs" in your local copy. All this, and a lot more, can be achieved with "transformable workspaces".
- Improved cloaked rules: Cloaking rules (defining cloaked.conf) lets you avoid some paths (files or directories) to be updated or downloaded at all. Now with simpler rules you can define flexible rules to include or exclude certain paths.
- Branch Explorer global configuration: Now the Branch Explorer can be globally configured for all users.
- Security: Being able to set permissions to repositories, branches, labels, paths is not only good to secure the codebase but also to enforce policies and best practices like "don't directly checkin to the release branch".
- Fine grained security with Access Control Lists (ACL): Using Plastic, you can set permissions to branches, labels, repositories, paths and even the server itself. Objects inherit in a hierarchical way (repository inherits from server, branch from its repo) so it is possible to configure very finely grained and flexible security policies. There is a list of more than 30 version control specific permissions like add, change, move, checkin, mergefrom, applylabel and more. Learn more here.
- Path based security: You can set permissions (ACLs) to specific paths so that they're always checked before performing certain operations. For instance, it is possible to deny the "ci" and "add" permissions at "/build/ scripts" for everyone except the "makefile masters" so that nobody messes with the build scripts. Path based permissions introduce several new possibilities together with the regular object ACLs. Check out the Security guide.
- Active Directory, LDAP and other authentication systems: Companies can integrate Plastic with their Windows Active Directory or LDAP system so that users, groups and authentications are handled by the operating system and not by Plastic. This way there is no need to import users periodically and any change in group assignments will be immediately detected by Plastic. Built-in user/password is also available for groups that don't use LDAP/AD or need to be independent from the IT department.
- SSL: Every Plastic server listens by default on a single TCP port, which makes it easy to configure and secure. It can be configured to listen on more ports including SSL, thus securing the communication between clients and servers or between different servers during replication.
- Auditing and compliance: Plastic keeps a configurable audit trail that register all important events happening in the system. Check out this article to find out how to comply with Sarbanes Oxley.
- Encrypted servers: This feature enables teams to use public servers because data will be stored in an encrypted way so that even if the server is compromised the attacker won't be able to access the original files. The mechanism is simple: you configure your team (or local) server to encrypt any file data being transferred to a given external server. It will also be decrypted while receiving from the encrypted server. The key will only be stored on your machine so unless it is compromised the data will be secured on external servers.
Click on the link below to download Plastic SCM NOW!
DOWNLOAD NOW !