GetBadges is a gamification platform targeted for software developers. This solution enables companies to create competitive games that can be integrated with their project management and developer tools.
$5
per user
Git
Score 10.0 out of 10
N/A
N/A
N/A
Plastic SCM
Score 8.2 out of 10
Enterprise companies (1,001+ employees)
Plastic SCM is a full stack version control system that aims to make software configuration easy. It focuses on enabling dev teams get work done by facilitating branching, diffing and merging. The vendor says that for those purposes it provides cross-platform apps and GUIs with: Branch explorer Diffing and merging tools (both syntactic and semantic) On-premises and cloud repo management Code review mergebots (last mile…
$6.95
per user
Pricing
GetBadges
Git
Plastic SCM
Editions & Modules
Enterprise
$5
per user
Company
$6
per user
SmallCompany
$7
per user
No answers on this topic
Cloud Edition
$6.95
per user
Team Edition (on prem)
$9.95
per user
Enterprise Edition
$23.25
per user
Enterprise Edition (perpetual)
$595.00
per user
Offerings
Pricing Offerings
GetBadges
Git
Plastic SCM
Free Trial
Yes
No
Yes
Free/Freemium Version
Yes
No
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
20% discount for annual subscription
—
* Educational institutions receive a substantial discount on Plastic SCM licensing fees
* Corporate/volume pricing is available
* For more information, please contact sales at sales@codicesoftware.com
More Pricing Information
Community Pulse
GetBadges
Git
Plastic SCM
Considered Multiple Products
GetBadges
No answer on this topic
Git
Verified User
Project Manager
Chose Git
Git is by far the best version control system out there. It's open source, free, and fast. No other version control system I've ever used has had all three features.
It’s helpful in engaging employees with their performance management and it boosts performance with gamification. This helps in production productivity as employees try to get more badges by competing with each other
GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
Plastic SCM is well suited for the distributed development environment, where branching and merging can easily be handled. Its a good tool for version controlling, especially for a big team which is contributing to a big project simultaneously. Situation where Plastic SCM is not at all well suited are : If the project is smaller one and need to be handled by couple of people. So in that case setting up Plastic SCM and educating people to work on it is not at all efficient
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
Best designed for medium to large companies with IT development teams using tools in the cloud, it provides gamification tools to boost performance at work.
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy. It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
Plastic has best integration with unity - zero issues, native, straightforward. GitHub feels more stable but for smaller and or indie teams plastic s version control feels much more under control - you click, you feel safe. moreover, there is no need for extra tools such as gitkraken, gitlab, Sourcetree, fork, etc. it is really easy to develop games this way.
Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.