GoCD vs. meshIQ

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

If you're involved in any business that is related to banking, insurance and lending industry, take the short way and save yourself from thousands of wasted dollars on fraud detection and application management issues, Nastel is my savior and it's the most powerful killer solution to beat the fraud and have a winning application performance management, It's like hiring a mathematics magician with super powers to help businesses get over the delayed amount of time spent on a problem, and the average time to process a claim, reduce errors and most importantly to decrease the number of tickets at the help center for a better and higher customer satisfaction score.

Incentivized

• 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

• Its ability to detect and correct IBM MQ issues before they effect the production.
• performance trends and statistics in real-time.
• Rapid and accurate monitoring of Command Servers, Dead Letter Queues, Queue Managers, Qdepth and Listeners.
• Built-in complex event processing to gain valuable visibility into order fulfillment processes

Incentivized

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

Incentivized

• The UI needs a lot of improvements to meet today's standards while keeping the functional part highly performing as it used to be
• Being unable to run reports through the workgroup security manager is a serious con, I think they need to consider giving it more attention
• the auto-monitoring feature performance goes low when it's enabled during a heavy workloads, it leads to a lower/heavier performance, but during the latest update I feel it got lighter somehow.
• They also need to give more attention to the encryption and enhance it with the latest encryption technologies

Incentivized

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

• 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

• A reduction in point of sale abandonment by 70% reflects the change in mindset of customers who are no longer irritated by price anomalies.
• The company was able to merge many unnecessary servers due to thousands of useless queues it had, resulting in yearly savings of more than $250,000
• improved efficiency and cost-savings by 80% within the first 2 months

Incentivized