Review Assistant is a peer code review tool which integrates with popular control systems namely: TFS, Subversion, Mercurial, Git and Perforce. It is an plugin for Visual Studio 2010, 2012, 2013, 2015 developed to enhance the team development process. The tool includes support for formal code review and allows users to add comments to a piece of code or to the entire review level. It allows teams to discuss code without scheduled meetings.
$349.95
GoCD
Score8 out of 10
N/A
GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
Combined with Code Compare and running Review Assistant on the TFS server, it provides a good way to share code and comments amount our team. It does everything we need it to do for code reviews and has a reporting tool.
Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Review Assistant does everything that I was hoping the default Visual Studio reviews would do. The iterations through accept/reject were the key winner.
The functionality for code reviews is great, especially the ability to comment on specific lines of code.
Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Microsoft provides a handy feature for code review inside the Visual Studio IDE. Review Assistant, though providing a similar code review user experience, supports work scenarios that are not covered by the Microsoft's IDE. Moreover, the version control systems support is broader in Review Assistant.
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
The tool saves a huge amount of time while reviewing the code. Review Assistant supports threaded comments, so team members can discuss code without scheduled meetings.
Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
