Code Compare is a compare tool designed to compare and merge differing files and folders. Code Compare integrates with source control systems: TFS, SVN, Git, Mercurial, and Perforce. Code Compare is shipped both as a standalone file diff tool and a Visual Studio extension.
N/A
Crucible
Score 10.0 out of 10
N/A
Atlasssian Crucible is a peer review tool for finding bugs and defects in version control tools Subversion, Git, Mercurial, CVS, and Perforce.
N/A
Pricing
Code Compare
Crucible
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Code Compare
Crucible
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Code Compare
Crucible
Considered Both Products
Code Compare
No answer on this topic
Crucible
Verified User
Anonymous
Chose Crucible
Not exactly an apples to apples comparison. Back when we were using SVN, Crucible was the go-to solution for code review. As we started moving to use Git and using pull requests (via Bitbucket), code review is now performed by using pull requests exclusively.
Crucible has a better look and feel for developers because it is web compatible and works well with IE or Chrome. Being that it is a web browser friendly, using Crucible is seamless and user-friendly. Github is an external tool on a different environment that requires more …
Crucible was first on the market and the price is inexpensive. Crucible integrates with Jira Software and Atlassian Fisheye, providing the ability to track defects efficiently. Sonarqube compares code to 'best standards' but not 'internal standards' and does not integrate to …
I think Crucible isn't quite as clean as Stash/Bitbucket, but it does some things better, like seeing individual commits easier. I also like how stash groups all comments on the overview of the Pull Request.
Gitlab and Github are very comparable to Crucible, and would probably be my first choice if those were the tools used for versioning as they are directly linked to git. Crucible was chosen by a current client and I had no choice in its selection. I would probably have chosen …
If your developer team is well-versed with standard VCS then I don't think they need this additional software to occupy their memory, they already have those capabilities within all VCS. A well-suited use case can be a team where not everybody has knowledge of VCS but has to collaborate on a project.
Depends on the version control and devops process your development teams adopt. Git (via Bitbucket, GitHub, GitLab, etc...) has become the new industry norm, and using pull requests can often provide the same code review features Crucible is used for. However, if you require code review beyond change/diff based (i.e. via pull request), then Crucible allows you to review code with more granular control, such as on per file basis.
It can sometimes be a bit slow to load. A server reboot for us tends to solve that issue. I'm not sure if it is a server issue, or maybe Crucible may have some caching issues.
I wish that you could easily stop the review creation process, rather than abandoning it.
Gitlab and GitHub are very comparable to Crucible, and would probably be my first choice if those were the tools used for versioning as they are directly linked to git. Crucible was chosen by a current client and I had no choice in its selection. I would probably have chosen GitHub if given a say.
I am not involved in the acquisition of Crucible so I cannot comment on the financial investment but I believe it is a necessary tool to have in any software shop, small or big.
As a developer, having Crucible as the code review process is a great asset and will save time and reduce risks which I believe is a positive return of investment.