GoCD vs. MadCap Flare

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.

Incentivized

Independently Invited by TrustRadius

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

MadCap Flare has its problems, but it serves our team well as an authoring software. This would not be the case if we needed to regularly collaborate on articles, as Flare is prone to conflict issues when another person dares to breathe near an open topic. When working individually, though, it's fine. I'd love to see improvements to design, performance, and stability, but Flare remains one of the best softwares on the market for our needs as an authoring team. MadCap Central is well-suited to internal reviewing when every member is comfortable with Flare (the errors it tends to introduce set aside). SMEs, though, tend to find it hard to use. It's cluttered, some styles don't render, and it just seems like a failed attempt to reproduce Google Docs. I'd love to see improvements there, to help get our SMEs to want to use Central.

Incentivized

Independently Invited by TrustRadius

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

• 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

Independently Invited by TrustRadius

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

• Single-sourcing
• Branching (GIT)
• Publishing and hosting

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

Incentivized

Independently Invited by TrustRadius

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

• I use it on a mac with windows parallel and it can be so buggy and laggy.
• I would love it if the software was entirely cloud-based, like Google Docs.
• Reviewing in Central is not a good experience, need better review functionality.

Incentivized

Independently Invited by TrustRadius

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

MadCap Flare is in desperate need of an overall redesign. It relies heavily on dozens and dozens of tiny buttons that contain dozens of nested features. Clicking the wrong button can cause your software to freeze and crash. Building targets can be an absolute mystery, as far as all the files involved. It also has a tendency to freeze and crash. There's typically a huge learning curve for new hires who've never used it--nothing is intuitive.

Incentivized

Independently Invited by TrustRadius

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

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.

Incentivized

Independently Invited by TrustRadius

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

MadCap software does offer quite a few more technical features than Google Drive, but the user experience is far inferior. Google Drive is much less buggy to work with, and it's much more accessible. MadCap only being available on Windows operating systems makes it difficult to work with teammates who may not have such a device available.

Incentivized

Independently Invited by TrustRadius

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

• 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

Independently Invited by TrustRadius

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

• We haven't measured this specifically