Review Assistant vs. GoCD

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.

GoCD is easy to set up. So if you just want to get some pipelines up & running quickly, & they're quite stable, or you can have many pipelines for different needs then GoCD is great. Still, if you only want to have a few pipelines, but with the flexibility to run them with different parameters dynamically, then Jenkins is better.

Incentivized

• 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.
• You don't have to leave the IDE.

• 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.

Incentivized

• Integration with JIRA is missing.
• Ability to search, filter and order comments.
• There is no support for Visual Studio Code.

• UI can be improved
• Location for settings can be re-arranged
• API for setting up pipeline

Incentivized

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.

I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The environment makes sense but can often confuse the user while GoCD simply has a drop-down to select your environment.

Incentivized

• 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.

• ROI has been good since it's open source
• 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

Incentivized