AccuRev, a software configuration management offering, is now owned and supported by Micro Focus since the December 2013 acquisition, and now by OpenText.
N/A
Pricing
Git
OpenText AccuRev
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Git
OpenText AccuRev
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Git
OpenText AccuRev
Considered Both Products
Git
Verified User
Engineer
Chose Git
GIT being a widely used tool have better reliability than its peers and have stands out when we compare it on operational performance criteria. GIT with speedy and extensive branching capabilities have helped developers to use check in their code quickly and space efficient way. G…
In my view, accurev ranks very low compared to other tools I have used. Microsoft TFS is the best in the industry as of today as it's a complete ALM solution. It does code version, bug tracking, user story documentation, and has easy integration with other external tools …
Git is one obvious alternative. However, Git is leveraging the command line and has minimal interface. Developer must be acclimated with command line in order to use Git.
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.
Very slow and not intuitive; it would be my last choice for version control systems.The UI is a little confusing at times and seems a little outdated. It needs a lot of improvement. It is suited for small projects and fewer number of projects. But if there are huge projects and many projects to be maintained in a portfolio, its a little hard to manage.
Ability to zoom in/out for stream-view. We currently have many streams/substreams and unable to view the entire workflow. Zooming in/out would benefit.
Being a designer, I use Adobe Flash and SWF files. When updating the SWF files, Accurev does not see these files as being changed and you will be unable to promote. In order to push changes, you must totally rename the SWF file.
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.
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.
In my view, accurev ranks very low compared to other tools I have used. Microsoft TFS is the best in the industry as of today as it's a complete ALM solution. It does code version, bug tracking, user story documentation, and has easy integration with other external tools supporting many languages. So I would definitely recommend TFS to anyone.
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.