Likelihood to Recommend 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.
Read full review PTC Integrity is an excellent source code management and version control tool, and I would suggest anyone to use it for that purpose. We can even define our workflows using individual forms for implementing Change Management, Defect Management and Access management requests. If properly used, this tool is great for managing our code for very long periods, considering my 4-5 years of usage. Though the UI could be better, and integration with some application servers could be better implemented, this tool is a good tool.
Read full review Pros Ability to create branches off current releases to modify code that can be tested in a separate environment. Each developer had their own local copy of branches so it minimizes mistakes being made. Has a user-friendly UI called Git Gui that users can use if they do not like using the command line. Conflicts are displayed nicely so that developers can resolve with ease. Read full review Helps to advance carefully through complicated and delicate process hives. Improve thereby our time-to-market knowledge transfers along our portfolio. Enhances the performances of single step in processes as well as the processes. Allows for unprecedented overview in broads and in depths. Steffen Jäschke Projektspezialist bei Steffen Jäschke EinzUnt Physik, Berechnungen
Read full review Cons There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master. Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this. Many different GUIs, many people (including myself) opt to just use the command-line. Read full review It can be overwhelming with the number of tabs, functions and ways to achieve the same result. The average user may struggle with learning the tool. The text editing in Integrity is weak and does not provide many options. Because of this, many user decide to use MS word instead, to document requirements. Read full review Likelihood to Renew 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.
Read full review I do not make decisions on what tool my company uses. I am just the user of the tool and such decisions are not handled by me. If I were to make such decisions, I would definitely renew MKS, considering the amount of data we have stored in MKS and the current number of users who are familiar with the system
Read full review Usability Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.
Read full review PTC Integrity comparatively could be considered a nice Source code management, Version controlling tool and could be compared with tools like StarTeam. If the integration to move/migrate code could be integrated into this tool, it would become an extremely powerful tool.
Read full review Support Rating 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.
Nate Dillon Front-End Web Developer, Office of Mediated Education
Read full review PTC Integrity administration can be somewhat daunting. They have been able to help with every question that I have submitted. Their support website is very easy to understand and submit questions and their phone support is wonderful
Read full review Implementation Rating It's easy to set up and get going.
Read full review I wasn't involved in implementation.
Read full review Alternatives Considered 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.
Read full review I think the reason that PTC Integrity was initially chosen is that it was the best product available in the mix at the time. This coupled with the PTC deal on multiple products was a no brainer based on the size and scope of potential users.
Read full review Return on Investment 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. Read full review MKS Integrity has proved to be particularly useful in the software development process by increasing employee effieciency MKS integrity has also made software development a very efficient process and makes feature releases and bug fixing a lot easier In addition to the above, our organization has been able to support manufacturing easily by reverting to a previous software version in case of an emergency. It has also led to faster time to market for new products. Read full review ScreenShots