MKS Integrity: To use or not to use.
July 09, 2014
MKS Integrity: To use or not to use.
Score 7 out of 10
Vetted Review
Verified User
Software Version
4.9.0.4745
Overall Satisfaction with PTC Integrity
It is used by the engineering department primarily for software development.
- Graphical file history representation
- Release management of software builds
- Change set management
- Hot fix and feature releases
- Main trunk is not protected and has no pre-conditions before committing a fix or feature to it.
- Conducting reviews is not possible. there is no avenue for people to comment on a check in
- When working with multiple snadboxes, the client seems to freeze up and needs to be started.
- 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.
Source Tree and Stash with Git.
MKS integrity does well in some areas such as merging changes into the main trunk and managing change sets. We actually selected Git after using MKS integrity for over 7 years.
MKS integrity does well in some areas such as merging changes into the main trunk and managing change sets. We actually selected Git after using MKS integrity for over 7 years.